public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/5130: gcc 3.1 bootstrap on x86 fails for over a month
Date: Sun, 16 Dec 2001 09:56:00 -0000 [thread overview]
Message-ID: <20011216175601.20911.qmail@sources.redhat.com> (raw)
The following reply was made to PR preprocessor/5130; it has been noted by GNATS.
From: Andreas Jaeger <aj@suse.de>
To: sefer@hotmail.com
Cc: gcc-gnats@gcc.gnu.org, hans_boehm@hp.com
Subject: Re: preprocessor/5130: gcc 3.1 bootstrap on x86 fails for over a
month
Date: Sun, 16 Dec 2001 18:53:00 +0100
sefer@hotmail.com writes:
>>Number: 5130
>>Category: preprocessor
[...]
>>Synopsis: gcc 3.1 bootstrap on x86 fails for over a month
> linux x86 (Mandrake 8.1)
>>Description:
> Hi!
>
> I've been following the gcc-3.1 cvs head development and for the past month the bootstrapping had failed with the following preprocessor error (past stage2 compilation):
>
> /home/zvi/t/abc/gcc/xgcc -B/home/zvi/t/abc/gcc/ -B/opt/gcc-3.1/i686-pc-linux-gnu/bin/ -B/opt/gcc-3.1/i686-pc-linux-gnu/lib/ -isystem /opt/gcc-3.1/i686-pc-linux-gnu/include -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DTHREAD_LOCAL_ALLOC=1 -DSILENT=1 -DNO_SIGNALS=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1 -DATOMIC_UNCOLLECTABLE=1 -I. -I../../../egcs/boehm-gc -I../../../egcs/boehm-gc/include -fexceptions -I././targ-include -I./../../../egcs/boehm-gc/./libc/includ e -g -O2 -c ../../../egcs/boehm-gc/obj_map.c -o obj_map.o >/dev/null 2>&1
> /bin/sh ./libtool --mode=compile /home/zvi/t/abc/gcc/xgcc -B/home/zvi/t/abc/gcc/ -B/opt/gcc-3.1/i686-pc-linux-gnu/bin/ -B/opt/gcc-3.1/i686-pc-linux-gnu/lib/ -isystem /opt/gcc-3.1/i686-pc-linux-gnu/include -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DTHREAD_LOCAL_ALLOC=1 -DSILENT=1 -DNO_SIGNALS=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1 -DATOMIC_UNCOLLECTABLE=1 -I. -I../../../egcs/boehm-gc -I../../../egcs/boehm-gc/include -fexceptions -I././targ-include -I. /../../../egcs/boehm-gc/./libc/include -g -O2 -c ../../../egcs/boehm-gc/os_dep.c
> /home/zvi/t/abc/gcc/xgcc -B/home/zvi/t/abc/gcc/ -B/opt/gcc-3.1/i686-pc-linux-gnu/bin/ -B/opt/gcc-3.1/i686-pc-linux-gnu/lib/ -isystem /opt/gcc-3.1/i686-pc-linux-gnu/include -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DTHREAD_LOCAL_ALLOC=1 -DSILENT=1 -DNO_SIGNALS=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1 -DATOMIC_UNCOLLECTABLE=1 -I. -I../../../egcs/boehm-gc -I../../../egcs/boehm-gc/include -fexceptions -I././targ-include -I./../../../egcs/boehm-gc/./libc/includ e -g -O2 -c ../../../egcs/boehm-gc/os_dep.c -fPIC -DPIC -o .libs/os_dep.o
> ../../../egcs/boehm-gc/os_dep.c:21:9: string constants are not valid in #if
> ../../../egcs/boehm-gc/os_dep.c:1854:9: string constants are not valid in #if
This does not fail on other i686 systems. What is different on your
system to the rest of the world?
Line 21 is:
# if (LINUX_VERSION_CODE <= 0x10400)
and line 1854:
# if (LINUX_VERSION_CODE >= 0x20100) && !defined(M68K) || defined(ALPHA) || defined(IA64)
Please tell us the contents of LINUX_VERSION_CODE for your system.
Hans, this kind of a hack should be replaced with something better.
glibc 2.2 gives you with the inclusion of <signal.h> struct sigcontext
- even on older kernels.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2001-12-16 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 9:56 Andreas Jaeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-16 9:53 neil
2001-12-16 9:06 sefer
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=20011216175601.20911.qmail@sources.redhat.com \
--to=aj@suse.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).