From: Sam Ravnborg <sam@ravnborg.org>
To: Alexander Kozyrev <kozyrev@junik.lv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel compilation
Date: Sat, 12 Nov 2005 23:22:13 +0100 [thread overview]
Message-ID: <20051112222213.GB10228@mars.ravnborg.org> (raw)
In-Reply-To: <200511121813.jACIDpXa055161@mail.junik.lv>
On Sat, Nov 12, 2005 at 08:13:40PM +0200, Alexander Kozyrev wrote:
> Linux asterisk1.local 2.6.9-11.EL #1 Wed Jun 8 16:59:52 CDT 2005 i686 i686
> i386 GNU/Linux
> After 2 hours of compilation -
> <......>
> CC lib/string.o
> CC lib/vsprintf.o
> AR lib/lib.a
> CC [M] lib/crc-ccitt.o
> CC [M] lib/libcrc32c.o
> LD arch/i386/lib/built-in.o
> CC arch/i386/lib/bitops.o
> AS arch/i386/lib/checksum.o
> CC arch/i386/lib/delay.o
> AS arch/i386/lib/getuser.o
> CC arch/i386/lib/memcpy.o
> CC arch/i386/lib/strstr.o
> CC arch/i386/lib/usercopy.o
> AR arch/i386/lib/lib.a
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> ld: kernel/built-in.o: No such file: No such file or directory
> make[1]: *** [.tmp_vmlinux1] Error 1
> make: *** [_all] Error 2
>
> 4 times with the same error.
You experienced a compile error in kernel/
Try
make kernel/
to see what is causing your trouble.
When something fails to build in kernel/ then built-in.o is not
made. And then the later build stages will fail.
I assume you are using make -J 2 (or higher)
PS. You do not need to do a make clean/ make mrproper - the result is
the same.
Sam
prev parent reply other threads:[~2005-11-12 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 18:13 Alexander Kozyrev
2005-11-12 22:22 ` Sam Ravnborg [this message]
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=20051112222213.GB10228@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kozyrev@junik.lv \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®