From: Jeff Garzik <jgarzik@pobox.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: sam@ravnborg.org, kai@tp1.ruhr-uni-bochum.de, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc for 2.5.59 bk
Date: Mon, 17 Feb 2003 13:36:59 -0500 [thread overview]
Message-ID: <3E512BCB.1010000@pobox.com> (raw)
In-Reply-To: <1911.212.181.176.76.1045505249.squirrel@www.zytor.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
H. Peter Anvin wrote:
>>On Sun, Feb 16, 2003 at 09:06:09PM -0600, Kai Germaschewski wrote:
>>
>>
>>>I did some work on integrating klibc into kbuild now. I used your
>>>patch as guide line, though I started from scratch with klibc-0.77.
>>>The build should work fine (reminder: "make KBUILD_VERBOSE=0 ..."
>>>will give you much more readable output), but I probably broke some
>>>non-x86 architectures in the process.
>>
>>Got this output when compiling user programs:
>> USERCC usr/lib/snprintf.o
>>cc1: warning: -malign-loops is obsolete, use -falign-loops
>>cc1: warning: -malign-jumps is obsolete, use -falign-jumps
>>cc1: warning: -malign-functions is obsolete, use -falign-functions
>>
>
>
> I get the same error compiling the kernel proper for Crusoe. This is what
> I like to call an "annoyance warning" where maintaining compatibility
> between gcc versions emit a neverending stream of annoying messages.
Maintaining gcc compatibility need not imply this annoyance. This has
been fixed in 2.5.x for ages, for the main kernel build, and I recently
fixed it in 2.4.x by the attached patch. We just need to move that fix
over to klibc build...
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1005 bytes --]
diff -Nru a/arch/i386/Makefile b/arch/i386/Makefile
--- a/arch/i386/Makefile Mon Feb 17 13:35:18 2003
+++ b/arch/i386/Makefile Mon Feb 17 13:35:18 2003
@@ -23,8 +23,10 @@
CFLAGS += -pipe
+check_gcc = $(shell if $(CC) $(1) -S -o /dev/null -xc /dev/null > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
+
# prevent gcc from keeping the stack 16 byte aligned
-CFLAGS += $(shell if $(CC) -mpreferred-stack-boundary=2 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-mpreferred-stack-boundary=2"; fi)
+CFLAGS += $(call check_gcc,-mpreferred-stack-boundary=2,)
ifdef CONFIG_M386
CFLAGS += -march=i386
@@ -83,7 +85,8 @@
endif
ifdef CONFIG_MCYRIXIII
-CFLAGS += -march=i486 -malign-functions=0 -malign-jumps=0 -malign-loops=0
+CFLAGS += $(call check_gcc,-march=c3,-march=i486)
+CFLAGS += $(call check_gcc,-falign-functions=0 -falign-jumps=0 -falign-loops=0,-malign-functions=0 -malign-jumps=0 -malign-loops=0)
endif
HEAD := arch/i386/kernel/head.o arch/i386/kernel/init_task.o
next prev parent reply other threads:[~2003-02-17 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 4:59 [RFC] klibc for 2.5.59 bk Greg KH
2003-02-07 5:06 ` H. Peter Anvin
2003-02-07 5:10 ` Greg KH
2003-02-07 15:00 ` Alex Riesen
2003-02-09 12:57 ` Greg KH
2003-02-17 3:06 ` Kai Germaschewski
2003-02-17 5:50 ` Jeff Garzik
2003-02-17 18:02 ` Sam Ravnborg
2003-02-17 18:07 ` H. Peter Anvin
2003-02-17 18:36 ` Jeff Garzik [this message]
2003-02-17 18:57 ` Sam Ravnborg
2003-02-17 19:24 ` Jeff Garzik
2003-02-18 8:58 ` H. Peter Anvin
2003-02-18 9:17 ` Jeff Garzik
2003-02-18 9:36 ` Stelian Pop
2003-02-18 9:37 ` Stelian Pop
2003-02-18 9:46 ` Jeff Garzik
2003-02-18 9:45 ` Jeff Garzik
2003-02-18 9:56 ` Stelian Pop
[not found] <20030217031008$3e63@gated-at.bofh.it>
[not found] ` <20030217031008$270a@gated-at.bofh.it>
2003-02-17 17:12 ` Arnd Bergmann
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=3E512BCB.1010000@pobox.com \
--to=jgarzik@pobox.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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