From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Sam Ravnborg <sam@ravnborg.org>,
Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kai@germaschewski.name
Subject: Re: 2.6.11-bk10 build problems
Date: Mon, 14 Mar 2005 12:34:30 -0800 [thread overview]
Message-ID: <566920000.1110832470@flay> (raw)
In-Reply-To: <20050314194930.GB17373@mars.ravnborg.org>
--On Monday, March 14, 2005 20:49:30 +0100 Sam Ravnborg <sam@ravnborg.org> wrote:
> On Mon, Mar 14, 2005 at 11:39:37AM -0800, Dave Hansen wrote:
>> I'm having some intermittent build problems on 2.6.11-bk10. First of
>> all, doing a 'make -j8 O=... install' errors out not being able to find
>> a vmlinux:
>>
>> $ make O=../mhp-build/i386-plain/ -j8 install
>> make[3]: *** No rule to make target `vmlinux', needed by
>> `arch/i386/boot/compressed/vmlinux.bin'. Stop.
>> make[2]: *** [arch/i386/boot/compressed/vmlinux] Error 2
>> make[1]: *** [install] Error 2
>> make: *** [install] Error 2
>>
>> Also, I just ran menuconfig, changed an option, and did another 'make
>> install', and it went straight to the install script with no
>> compiling.
>>
>> Note that these are with O=, so it might be just a separate build tree
>> problem.
>>
>> Any ideas?
>
> On popular request 'make install' no longer try to update vmlinux.
> This is to avoid errornous recompilation when installing the kernel
> as root especially when fetching kernel via nfs where path may have
> changed.
That's frigging annoying. It's worked that way for ages, and all our
scripts assume it works.
Andrew, can we back that out?
M.
next prev parent reply other threads:[~2005-03-14 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 19:39 2.6.11-bk10 build problems Dave Hansen
2005-03-14 19:49 ` Sam Ravnborg
2005-03-14 19:57 ` Dave Hansen
2005-03-14 20:34 ` Martin J. Bligh [this message]
2005-03-14 21:22 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2005-03-14 21:31 Martin J. Bligh
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=566920000.1110832470@flay \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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