From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@zytor.com>, klibc@zytor.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] klibc for 2.5.63
Date: Mon, 3 Mar 2003 21:26:18 +0100 [thread overview]
Message-ID: <20030303202618.GA15819@mars.ravnborg.org> (raw)
In-Reply-To: <b3ego8$eac$1@cesium.transmeta.com>
On Mon, Feb 24, 2003 at 05:26:32PM -0800, H. Peter Anvin wrote:
> Greg has taken on the job of integrating klibc with the kernel, but
> please post klibc bug reports to the klibc mailing list at
> <klibc@zytor.com>.
To avoid annoying warning from gcc I had to check for compatibility with
-falign-* like we do in arch/i386/Makefile.
check_usergcc located in top-level makefile to allow other architectures
to use it later.
Also modified a few assignment to use :=.
On top of Gregh's latest bk tree.
Sam
===== Makefile 1.385 vs edited =====
--- 1.385/Makefile Mon Mar 3 18:17:13 2003
+++ edited/Makefile Mon Mar 3 21:18:11 2003
@@ -933,4 +933,7 @@
# Usage is deprecated, because make does not see this as an invocation of make.
descend =$(Q)$(MAKE) -f scripts/Makefile.build obj=$(1) $(2)
+check_usergcc = $(shell if $(USERCC) $(1) -S -o /dev/null -xc /dev/null > \
+ /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
+
FORCE:
===== usr/lib/arch/i386/MCONFIG 1.1 vs edited =====
--- 1.1/usr/lib/arch/i386/MCONFIG Sat Feb 15 23:53:51 2003
+++ edited/usr/lib/arch/i386/MCONFIG Mon Mar 3 21:18:08 2003
@@ -13,12 +13,19 @@
# them to be cdecl
# REGPARM = -mregparm=3 -DREGPARM
-OPTFLAGS = $(REGPARM) -march=i386 -Os -fomit-frame-pointer \
- -malign-functions=0 -malign-jumps=0 -malign-loops=0
-BITSIZE = 32
+#check_usergcc = $(shell if $(USERCC) $(1) -S -o /dev/null -xc /dev/null > \
+ /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
+
+
+OPTFLAGS := $(REGPARM) -march=i386 -Os -fomit-frame-pointer
+OPTFLAGS += $(call check_usergcc, \
+ -falign-functions=0 -falign-jumps=0 -falign-loops=0, \
+ -malign-functions=0 -malign-jumps=0 -malign-loops=0)
+
+BITSIZE := 32
# Extra linkflags when building the shared version of the library
# This address needs to be reachable using normal inter-module
# calls, and work on the memory models for this architecture
# 96 MB - normal binaries start at 128 MB
-SHAREDFLAGS = -Ttext 0x06000200
+SHAREDFLAGS := -Ttext 0x06000200
next prev parent reply other threads:[~2003-03-03 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 22:56 [BK PATCH] klibc for 2.5.63 Greg KH
2003-02-25 1:26 ` H. Peter Anvin
2003-02-26 22:53 ` Bill Davidsen
2003-02-26 23:01 ` H. Peter Anvin
2003-03-03 20:26 ` Sam Ravnborg [this message]
2003-03-03 19:28 ` Greg KH
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=20030303202618.GA15819@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@zytor.com \
--cc=klibc@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).