From: Adrian Bunk <bunk@stusta.de>
To: Christian <evil@g-house.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 5 compile errors for 2.4-BK
Date: Tue, 2 Nov 2004 18:33:37 +0100 [thread overview]
Message-ID: <20041102173337.GG4978@stusta.de> (raw)
In-Reply-To: <41879488.10601@g-house.de>
On Tue, Nov 02, 2004 at 03:07:04PM +0100, Christian wrote:
> every day my scripts compile several kernel from the latest -BK tree,
> since oct, 30. there are 5 compile errors shown in:
>
> make[3]: [neighbour.o] Error 1 (ignored)
> make[3]: [core.o] Error 1 (ignored)
> make[3]: [arp.o] Error 1 (ignored)
> make[3]: [ipv4.o] Error 1 (ignored)
> make[1]: [first_rule] Error 2 (ignored)
>
> [and that's why these 2 occur too:]
>
> make: [vmlinux] Error 1 (ignored)
> make: [zImage] Error 2 (ignored)
This part of the errors alone is useless.
> full make logs, configs here:
>...
> this is all with debian/unstable, using gcc-3.4.2, binutils-2.15 (both
>...
Did you manually change your gcc link or are you using gcc 3.3 ?
> maybe someone may find this useful...
Other people already do similar things.
The interesting thing is the exact error message. Your 5 errors are
actually only two (similar) compile errors.
For being really useful, a posting of the error messages of the two
actual error messages would be useful. If you trace down who is "guilty"
for the compile error and Cc the person in question it's even better
(but please check linux-kernel before being the tenth person reporting
the same issue).
> thanks,
> Christian.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-11-02 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 14:07 5 compile errors for 2.4-BK Christian
2004-11-02 17:33 ` Adrian Bunk [this message]
2004-11-03 13:55 ` Christian Kujau
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=20041102173337.GG4978@stusta.de \
--to=bunk@stusta.de \
--cc=evil@g-house.de \
--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