From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] janitor project: fix warnings
Date: Mon, 20 Dec 2004 09:32:28 +0000 [thread overview]
Message-ID: <41C69C2C.5060506@bfs.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
mmmh,
i have no problem to test other ppl software and fixing warnings is a
good thing.
does this mean we will have a linux kernel compiling without warnings in
future ? We should define this as a target. i had no reply for my last
patches in that sense and assumed they were to unimportant.
re,
walter
ps: is it ok to ask/discuss problems with e.g. binutils on the list ?
i had some problems with ld on alpha (crashes compiling linux kernel
because of GOT problems). the maintainer was not happy as i told him to
recompile the linux kernel :( but if found no other way to reproduce the
error.
Andi Kleen wrote:
> On Mon, Dec 20, 2004 at 12:15:39AM +0200, Alexey Dobriyan wrote:
>
>>On Sunday 19 December 2004 21:09, Andi Kleen wrote:
>>
>>
>>>make allmodconfig
>>>make CC=/usr/local/gcc4/bin/gcc 2>&1 | tee LOG
>>
>> CC kernel/acct.o
>>kernel/acct.c: In function ???encode_float???:
>>kernel/acct.c:366: fatal error: internal consistency failure
>>compilation terminated.
>
>
> I checked this and it doesn't seem to happen with my compiler
> (which is a newer CVS checkout). So I assume it has been fixed already.
>
> -Andi
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/kernel-janitors
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
reply other threads:[~2004-12-20 9:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41C69C2C.5060506@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.