From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Avuton Olrich <avuton@gmail.com>,
Russell Whitaker <russ@ashlandhome.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.19 + gcc-4.1.1
Date: Wed, 14 Jun 2006 00:27:43 -0400 [thread overview]
Message-ID: <448F903F.9070108@ens-lyon.org> (raw)
In-Reply-To: <20060614042007.GD13255@w.ods.org>
Willy Tarreau wrote:
> On Wed, Jun 14, 2006 at 12:10:59AM -0400, Brice Goglin wrote:
>
>> Avuton Olrich wrote:
>>
>>> On 6/13/06, Russell Whitaker <russ@ashlandhome.net> wrote:
>>>
>>>> Then, after mrproper, rebuilt with gcc-4.1.1, no other changes.
>>>> compiles ok, installs ok. But, when attempting to load a module, get
>>>> the following message: version magic '2.6.16.19via K6 gcc-4.1',
>>>> should be '2.6.16.19via 486 gcc-3.3'
>>>>
>>> You may have forgotten to "make modules modules_install"
>>>
>> Actually, "make modules" does not exist anymore with 2.6. Both built-in
>> and modular stuff are built at the same time.
>> Only "make modules_install" is still required.
>>
>
> What's this bullshit ?
>
> $ grep ^modules: Makefile
> modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
> modules: $(module-dirs)
>
Sorry, my mistake. Didn't know the target still existed. Anyway, "make"
now implies "make modules" so the latter is not required anymore as long
as you fully rebuild your kernel using the former (which I assume
Russell did since he changed his compiler).
Brice
next prev parent reply other threads:[~2006-06-14 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 2:23 Russell Whitaker
2006-06-14 3:49 ` Avuton Olrich
2006-06-14 4:10 ` Brice Goglin
2006-06-14 4:20 ` Willy Tarreau
2006-06-14 4:27 ` Brice Goglin [this message]
2006-06-16 19:43 ` Russell Whitaker
2006-06-14 5:09 ` Russell Whitaker
2006-06-14 9:33 ` Jan Engelhardt
2006-06-14 17:06 ` Alistair John Strachan
2006-06-14 5:24 ` Tino Keitel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=448F903F.9070108@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=avuton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=russ@ashlandhome.net \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®