From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Brice Goglin <Brice.Goglin@ens-lyon.org>,
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 18:06:25 +0100 [thread overview]
Message-ID: <200606141806.25124.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0606141132190.5349@yvahk01.tjqt.qr>
On Wednesday 14 June 2006 10:33, Jan Engelhardt wrote:
> >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.
>
> You can _still_ build bzImage and modules separately.
>
> The _default_ kernel Makefile target though reads (sth. like)
>
> all: bzImage modules
Maybe for consistency with other packages, the default "make install" should
imply modules_install too.
I know you can hack around this with /sbin/installkernel (on at least x86 and
x86_64), but it's counterintuitive. I guess the reason is that 'install' has
always meant "just the bzImage please", and sometimes it's valid to install
only a bzImage without reinstalling modules. However, it just leads to
problems such at the original poster's.
--
Cheers,
Alistair.
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-06-14 17:06 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
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 [this message]
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=200606141806.25124.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=Brice.Goglin@ens-lyon.org \
--cc=avuton@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=russ@ashlandhome.net \
/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®