From: "O.Sezer" <sezero@superonline.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-pre7-pac1
Date: Mon, 13 Oct 2003 21:48:41 +0300 [thread overview]
Message-ID: <3F8AF389.80600@superonline.com> (raw)
If I listen to the evil whispers and say "m" to CONFIG_IP_SCTP,
then my build logs are spammed by messages like the following:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.23-pre7-pac1/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=pentium3 -nostdinc -iwithprefix include -DKBUILD_BASENAME=md -DEXPORT_SYMTAB -c md.c
In file included from /usr/src/linux-2.4.23-pre7-pac1/include/net/sctp/ulpevent.h:51,
from /usr/src/linux-2.4.23-pre7-pac1/include/net/sctp/structs.h:93,
from /usr/src/linux-2.4.23-pre7-pac1/include/net/sock.h:53,
from /usr/src/linux-2.4.23-pre7-pac1/include/net/ip.h:39,
from /usr/src/linux-2.4.23-pre7-pac1/include/net/checksum.h:31,
from /usr/src/linux-2.4.23-pre7-pac1/include/linux/raid/md.h:35,
from md.c:33:
/usr/src/linux-2.4.23-pre7-pac1/include/net/sctp/compat.h:74: warning: static declaration for `generic_fls' follows non-static
Since there are no changes to stcp code in -pac, this should also
be a problem for mainline.
Regards,
Özkan Sezer
next reply other threads:[~2003-10-13 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 18:48 O.Sezer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-13 18:41 2.4.23-pre7-pac1 O.Sezer
2003-10-13 12:28 2.4.23-pre7-pac1 O.Sezer
2003-10-14 11:53 ` 2.4.23-pre7-pac1 Bernhard Rosenkraenzer
2003-10-12 22:18 2.4.23-pre7-pac1 Bernhard Rosenkraenzer
2003-10-12 23:01 ` 2.4.23-pre7-pac1 Marcos D. Marado Torres
2003-10-13 8:27 ` 2.4.23-pre7-pac1 Zwane Mwaikambo
2003-10-13 10:38 ` 2.4.23-pre7-pac1 Marcos D. Marado Torres
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=3F8AF389.80600@superonline.com \
--to=sezero@superonline.com \
--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 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.