From: "M.H.VanLeeuwen" <vanl@megsinet.net>
To: gcc-help@gcc.gnu.org
Cc: vanl@megsinet.net
Subject: 2.95.2 GCC fails bootstrap compile on x86
Date: Mon, 10 Jan 2000 20:51:00 -0000 [thread overview]
Message-ID: <387AB3A3.19EEBB60@megsinet.net> (raw)
Hi,
I've tried both 2.95.1/2 and have been unable to successfully install
GCC. I've
had no problems compiling other programs and egcs-1.1.2 recompiles just
fine.
I've rebuilt and reinstalled glibc-2.1.2 after moving the old
/usr/include out of
the way...now i'm not sure what to do.
Any suggestions would be appreciated
Martin
System info:
Kernel x86 2.2.13
Kernel modules 2.1.121
Gnu C egcs-2.91.66
Binutils 2.9.5.0.16
Linux C Library 1.2.so*
Dynamic linker ldd (GNU libc) 2.1.2
Linux C++ Library 2.9.0*
Procps 2.0.2
Mount 2.10b
Net-tools 1.53
Kbd 1.00
Sh-utils 2.0
make bootstrap
[snip]
make[1]: Leaving directory `/tmp/gcc-2.95.2/heli/texinfo'
Bootstrapping the compiler
make[1]: Entering directory `/tmp/gcc-2.95.2/heli/gcc'
make CC="gcc" libdir=/usr/lib LANGUAGES="c "
make[2]: Entering directory `/tmp/gcc-2.95.2/heli/gcc'
gcc -DIN_GCC -g -DHAVE_CONFIG_H -I. -I../../gcc
-I../../gcc/config -I..
/../gcc/../include \
-DGCC_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/include\"
\
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../.
.`echo /usr | sed -e 's|^/usr||' -e 's|/[^/]*|/..|g'`/include/g++-3\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../i5
86-pc-linux-gnu/sys-include\" \
-DTOOL_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../i58
6-pc-linux-gnu/include\" \
-c `echo ../../gcc/cccp.c | sed 's,^\./,,'`
In file included from /usr/include/stdio.h:57,
from ../../gcc/system.h:32,
from ../../gcc/cccp.c:23:
/usr/include/libio.h:363: conflicting types for `__restrict'
/usr/include/libio.h:363: previous declaration of `__restrict'
/usr/include/libio.h:364: conflicting types for `__restrict'
/usr/include/libio.h:363: previous declaration of `__restrict'
/usr/include/libio.h:365: conflicting types for `__restrict'
/usr/include/libio.h:365: previous declaration of `__restrict'
In file included from ../../gcc/system.h:32,
from ../../gcc/cccp.c:23:
/usr/include/stdio.h:178: parse error before `__filename'
/usr/include/stdio.h:181: parse error before `__filename'
/usr/include/stdio.h:228: parse error before `__stream'
/usr/include/stdio.h:232: parse error before `__stream'
/usr/include/stdio.h:238: parse error before `__stream'
/usr/include/stdio.h:247: parse error before `__stream'
/usr/include/stdio.h:250: parse error before `__format'
/usr/include/stdio.h:252: parse error before `__s'
/usr/include/stdio.h:256: parse error before `__s'
/usr/include/stdio.h:260: parse error before `__format'
/usr/include/stdio.h:263: parse error before `__s'
/usr/include/stdio.h:269: parse error before `__s'
/usr/include/stdio.h:273: parse error before `__s'
/usr/include/stdio.h:277: parse error before `__s'
/usr/include/stdio.h:306: parse error before `__stream'
/usr/include/stdio.h:309: parse error before `__format'
/usr/include/stdio.h:311: parse error before `__s'
/usr/include/stdio.h:389: parse error before `__s'
/usr/include/stdio.h:424: parse error before `__s'
/usr/include/stdio.h:442: parse error before `__ptr'
/usr/include/stdio.h:445: parse error before `__ptr'
/usr/include/stdio.h:450: parse error before `__ptr'
/usr/include/stdio.h:452: parse error before `__ptr'
/usr/include/stdio.h:495: parse error before `__stream'
In file included from ../../gcc/system.h:132,
from ../../gcc/cccp.c:23:
[snip]
WARNING: multiple messages have this Message-ID
From: "M.H.VanLeeuwen" <vanl@megsinet.net>
To: gcc-help@gcc.gnu.org
Cc: vanl@megsinet.net
Subject: 2.95.2 GCC fails bootstrap compile on x86
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <387AB3A3.19EEBB60@megsinet.net> (raw)
Message-ID: <20000401000000.dgvtvWDvM5h1sbFoqAJ8XMA57DS7peFr-bakkXfeZaE@z> (raw)
Hi,
I've tried both 2.95.1/2 and have been unable to successfully install
GCC. I've
had no problems compiling other programs and egcs-1.1.2 recompiles just
fine.
I've rebuilt and reinstalled glibc-2.1.2 after moving the old
/usr/include out of
the way...now i'm not sure what to do.
Any suggestions would be appreciated
Martin
System info:
Kernel x86 2.2.13
Kernel modules 2.1.121
Gnu C egcs-2.91.66
Binutils 2.9.5.0.16
Linux C Library 1.2.so*
Dynamic linker ldd (GNU libc) 2.1.2
Linux C++ Library 2.9.0*
Procps 2.0.2
Mount 2.10b
Net-tools 1.53
Kbd 1.00
Sh-utils 2.0
make bootstrap
[snip]
make[1]: Leaving directory `/tmp/gcc-2.95.2/heli/texinfo'
Bootstrapping the compiler
make[1]: Entering directory `/tmp/gcc-2.95.2/heli/gcc'
make CC="gcc" libdir=/usr/lib LANGUAGES="c "
make[2]: Entering directory `/tmp/gcc-2.95.2/heli/gcc'
gcc -DIN_GCC -g -DHAVE_CONFIG_H -I. -I../../gcc
-I../../gcc/config -I..
/../gcc/../include \
-DGCC_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/include\"
\
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../.
.`echo /usr | sed -e 's|^/usr||' -e 's|/[^/]*|/..|g'`/include/g++-3\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../i5
86-pc-linux-gnu/sys-include\" \
-DTOOL_INCLUDE_DIR=\"/usr/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/../../../../i58
6-pc-linux-gnu/include\" \
-c `echo ../../gcc/cccp.c | sed 's,^\./,,'`
In file included from /usr/include/stdio.h:57,
from ../../gcc/system.h:32,
from ../../gcc/cccp.c:23:
/usr/include/libio.h:363: conflicting types for `__restrict'
/usr/include/libio.h:363: previous declaration of `__restrict'
/usr/include/libio.h:364: conflicting types for `__restrict'
/usr/include/libio.h:363: previous declaration of `__restrict'
/usr/include/libio.h:365: conflicting types for `__restrict'
/usr/include/libio.h:365: previous declaration of `__restrict'
In file included from ../../gcc/system.h:32,
from ../../gcc/cccp.c:23:
/usr/include/stdio.h:178: parse error before `__filename'
/usr/include/stdio.h:181: parse error before `__filename'
/usr/include/stdio.h:228: parse error before `__stream'
/usr/include/stdio.h:232: parse error before `__stream'
/usr/include/stdio.h:238: parse error before `__stream'
/usr/include/stdio.h:247: parse error before `__stream'
/usr/include/stdio.h:250: parse error before `__format'
/usr/include/stdio.h:252: parse error before `__s'
/usr/include/stdio.h:256: parse error before `__s'
/usr/include/stdio.h:260: parse error before `__format'
/usr/include/stdio.h:263: parse error before `__s'
/usr/include/stdio.h:269: parse error before `__s'
/usr/include/stdio.h:273: parse error before `__s'
/usr/include/stdio.h:277: parse error before `__s'
/usr/include/stdio.h:306: parse error before `__stream'
/usr/include/stdio.h:309: parse error before `__format'
/usr/include/stdio.h:311: parse error before `__s'
/usr/include/stdio.h:389: parse error before `__s'
/usr/include/stdio.h:424: parse error before `__s'
/usr/include/stdio.h:442: parse error before `__ptr'
/usr/include/stdio.h:445: parse error before `__ptr'
/usr/include/stdio.h:450: parse error before `__ptr'
/usr/include/stdio.h:452: parse error before `__ptr'
/usr/include/stdio.h:495: parse error before `__stream'
In file included from ../../gcc/system.h:132,
from ../../gcc/cccp.c:23:
[snip]
next reply other threads:[~2000-01-10 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 20:51 M.H.VanLeeuwen [this message]
2000-04-01 0:00 ` M.H.VanLeeuwen
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=387AB3A3.19EEBB60@megsinet.net \
--to=vanl@megsinet.net \
--cc=gcc-help@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).