From: Guardian <guardianNOSTUFF@sdf.lonestar.org>
To: help-gcc@gnu.org
Subject: Internal compiler error
Date: Wed, 29 Sep 1999 12:58:00 -0000 [thread overview]
Message-ID: <37F26D1D.5D0D6500@sdf.lonestar.org> (raw)
Comments: Buggy compiler, how to compile a compiler with a buggy
compiler, what do I need to upgrade on Slackware 4.0
--
Trying to compile gcc2.95.1
While doing make bootstrap....
make[2]: Entering directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnulibc1/bin/
-DIN_GCC -DUSE_GNULIBC_1 -O2 -g -O2 -DHAVE_CONFIG_H -I.
-I/usr/local/src/gcc-2.95.1/gcc -I/usr/local/src/gcc-2.95.1/gcc/config
-I/usr/local/src/gcc-2.95.1/gcc/../include \
-DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/include\"
\
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../..`echo
/usr/local | sed -e 's|^/usr/local||' -e
's|/[^/]*|/..|g'`/include/g++-3\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../../i686-pc-linux-gnulibc1/sys-include\"
\
-DTOOL_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../../i686-pc-linux-gnulibc1/include\"
\
-c `echo /usr/local/src/gcc-2.95.1/gcc/cccp.c | sed 's,^\./,,'`
xgcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [cccp.o] Error 1
make[2]: Leaving directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
make: *** [bootstrap] Error 2
This is one reason I want to upgrade my compiler. I did get qt 2.0 to
compile but I had to disable optimize. I do want to optimize since going
to all the trouble to compile. So, this is the main reason for
upgrading to gcc.2.95.1
What's wrong with this compiler? Do I even need a native compiler to
compile gcc-full? It say you must have automake, autoconfig, and
binutils, what else?
This has got me so confused I don't know what to do. I can't compile
shit without going through a lot of trouble to get it to work. Then
it's not compiled the way I want it; such as, no optimized code. I can
find no updates for Slackware native packages anywhere; only newer or
beta distributions. Must I upgrade my slackware distribution everytime
I need an overhaul? Beside, that won't work cause the latest beta don't
include what I want to install.
My system: 233mhz Cyrix, 96megs ram, two 120meg swap partitions, and a
full Slackware 4.0 install.
Note: if I install binaries, well that would NOT fix my compiler
problem, now would it.
My current gcc usually dumps out most large g++ sources. Has anyone had
this problem?
Thanks,
Guardian
remove the obvious.
WARNING: multiple messages have this Message-ID
From: Guardian <guardianNOSTUFF@sdf.lonestar.org>
To: help-gcc@gnu.org
Subject: Internal compiler error
Date: Thu, 30 Sep 1999 23:56:00 -0000 [thread overview]
Message-ID: <37F26D1D.5D0D6500@sdf.lonestar.org> (raw)
Message-ID: <19990930235600.DPPNR3XG-0qD8AGe22dgywufEUz2O8iiSFiFV3rSU4s@z> (raw)
Comments: Buggy compiler, how to compile a compiler with a buggy
compiler, what do I need to upgrade on Slackware 4.0
--
Trying to compile gcc2.95.1
While doing make bootstrap....
make[2]: Entering directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnulibc1/bin/
-DIN_GCC -DUSE_GNULIBC_1 -O2 -g -O2 -DHAVE_CONFIG_H -I.
-I/usr/local/src/gcc-2.95.1/gcc -I/usr/local/src/gcc-2.95.1/gcc/config
-I/usr/local/src/gcc-2.95.1/gcc/../include \
-DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/include\"
\
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../..`echo
/usr/local | sed -e 's|^/usr/local||' -e
's|/[^/]*|/..|g'`/include/g++-3\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../../i686-pc-linux-gnulibc1/sys-include\"
\
-DTOOL_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../../i686-pc-linux-gnulibc1/include\"
\
-c `echo /usr/local/src/gcc-2.95.1/gcc/cccp.c | sed 's,^\./,,'`
xgcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [cccp.o] Error 1
make[2]: Leaving directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
make: *** [bootstrap] Error 2
This is one reason I want to upgrade my compiler. I did get qt 2.0 to
compile but I had to disable optimize. I do want to optimize since going
to all the trouble to compile. So, this is the main reason for
upgrading to gcc.2.95.1
What's wrong with this compiler? Do I even need a native compiler to
compile gcc-full? It say you must have automake, autoconfig, and
binutils, what else?
This has got me so confused I don't know what to do. I can't compile
shit without going through a lot of trouble to get it to work. Then
it's not compiled the way I want it; such as, no optimized code. I can
find no updates for Slackware native packages anywhere; only newer or
beta distributions. Must I upgrade my slackware distribution everytime
I need an overhaul? Beside, that won't work cause the latest beta don't
include what I want to install.
My system: 233mhz Cyrix, 96megs ram, two 120meg swap partitions, and a
full Slackware 4.0 install.
Note: if I install binaries, well that would NOT fix my compiler
problem, now would it.
My current gcc usually dumps out most large g++ sources. Has anyone had
this problem?
Thanks,
Guardian
remove the obvious.
WARNING: multiple messages have this Message-ID
From: Guardian <guardianNOSTUFF@sdf.lonestar.org>
To: help-gcc@gnu.org
Subject: Internal compiler error
Date: Fri, 01 Oct 1999 00:00:00 -0000 [thread overview]
Message-ID: <37F26D1D.5D0D6500@sdf.lonestar.org> (raw)
Message-ID: <19991001000000.uQUtZn2FsD6po2pO-KDQ9xb3armArCPDlVOeGDUFZro@z> (raw)
Comments: Buggy compiler, how to compile a compiler with a buggy
compiler, what do I need to upgrade on Slackware 4.0
--
Trying to compile gcc2.95.1
While doing make bootstrap....
make[2]: Entering directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnulibc1/bin/
-DIN_GCC -DUSE_GNULIBC_1 -O2 -g -O2 -DHAVE_CONFIG_H -I.
-I/usr/local/src/gcc-2.95.1/gcc -I/usr/local/src/gcc-2.95.1/gcc/config
-I/usr/local/src/gcc-2.95.1/gcc/../include \
-DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/include\"
\
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../..`echo
/usr/local | sed -e 's|^/usr/local||' -e
's|/[^/]*|/..|g'`/include/g++-3\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../../i686-pc-linux-gnulibc1/sys-include\"
\
-DTOOL_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnulibc1/2.95.1/../../../../i686-pc-linux-gnulibc1/include\"
\
-c `echo /usr/local/src/gcc-2.95.1/gcc/cccp.c | sed 's,^\./,,'`
xgcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [cccp.o] Error 1
make[2]: Leaving directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/usr/local/src/gcc-2.95.1/objdir/gcc'
make: *** [bootstrap] Error 2
This is one reason I want to upgrade my compiler. I did get qt 2.0 to
compile but I had to disable optimize. I do want to optimize since going
to all the trouble to compile. So, this is the main reason for
upgrading to gcc.2.95.1
What's wrong with this compiler? Do I even need a native compiler to
compile gcc-full? It say you must have automake, autoconfig, and
binutils, what else?
This has got me so confused I don't know what to do. I can't compile
shit without going through a lot of trouble to get it to work. Then
it's not compiled the way I want it; such as, no optimized code. I can
find no updates for Slackware native packages anywhere; only newer or
beta distributions. Must I upgrade my slackware distribution everytime
I need an overhaul? Beside, that won't work cause the latest beta don't
include what I want to install.
My system: 233mhz Cyrix, 96megs ram, two 120meg swap partitions, and a
full Slackware 4.0 install.
Note: if I install binaries, well that would NOT fix my compiler
problem, now would it.
My current gcc usually dumps out most large g++ sources. Has anyone had
this problem?
Thanks,
Guardian
remove the obvious.
next reply other threads:[~1999-09-29 12:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 12:58 Guardian [this message]
1999-09-30 3:33 ` jwk
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
1999-10-01 13:49 ` Guardian
1999-10-31 13:57 ` Guardian
1999-09-30 23:56 ` Guardian
1999-10-01 0:00 ` Guardian
2001-07-02 8:04 Av Vl
2001-07-03 8:36 Av Vl
2003-07-30 20:29 DEEPA SIVASANKARANE
2008-02-29 21:27 internal " raian.ufop
2008-02-29 22:16 ` Brian Dessent
2008-03-03 18:50 ` raian.ufop
2010-07-12 9:04 Malte.Mauelshagen
2010-07-12 9:56 ` Ian Lance Taylor
2012-12-24 16:44 Internal Compiler Error tanle
2012-12-24 18:19 ` Andrew Haley
2012-12-27 17:27 ` Iyer, Balaji V
2018-01-19 13:17 internal compiler error Matt Sexton via gcc-help
2018-01-19 13:26 ` Mikhail Maltsev
2018-01-19 14:35 ` Matt Sexton via gcc-help
2018-01-19 15:54 ` Matt Sexton via gcc-help
2018-01-22 13:14 ` Mason
2018-01-22 13:21 ` Matt Sexton via gcc-help
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=37F26D1D.5D0D6500@sdf.lonestar.org \
--to=guardiannostuff@sdf.lonestar.org \
--cc=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).