[SLE] Compile problem after installing 7.0
System Specs: AMD K62/400 128 MB 100MHz SDRAM 8GB IDE HDD Matrox G400-MAX 32MB Problem: I am having a problem compiling anything after installing SuSE 7.0 Pro. First I upgraded from 6.4 - 7.0 and experienced the problem. However after a clean install of 7.0 I am still experiencing the problem. gcc gives the following error randomly throughout compile time. I am able to start the build again and it will continue past the last stop point and randomly stop again. The following occurred while compiling kernel 2.4.0-test7: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=k6 -fno-strict-aliasing -c -o prints.o prints.c prints.c: In function `sprintf_le_key': prints.c:90: Internal compiler error in `find_basic_blocks_1', at flow.c:732 Please submit a full bug report. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. cpp: output pipe has been closed This problem is repeatable with any program that need to be compiled. I have tried the stock 7.0 install, as well as upgrading libc to 2.1.3-154 with no luck. Anyone have a similar problem? Any help would be appreciated. -- Mike Moulton -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hello Mike, on Wednesday, October 11, 2000 at 22:47:00 -0700, you sat in front of your keyboard and wrote:
System Specs:
AMD K62/400 128 MB 100MHz SDRAM 8GB IDE HDD Matrox G400-MAX 32MB
Problem:
I am having a problem compiling anything after installing SuSE 7.0 Pro. First I upgraded from 6.4 - 7.0 and experienced the problem. However after a clean install of 7.0 I am still experiencing the problem.
gcc gives the following error randomly throughout compile time. I am able to start the build again and it will continue past the last stop point and randomly stop again.
The following occurred while compiling kernel 2.4.0-test7:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=k6 -fno-strict-aliasing -c -o prints.o prints.c prints.c: In function `sprintf_le_key': prints.c:90: Internal compiler error in `find_basic_blocks_1', at flow.c:732 Please submit a full bug report. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. cpp: output pipe has been closed
This problem is repeatable with any program that need to be compiled. I have tried the stock 7.0 install, as well as upgrading libc to 2.1.3-154 with no luck.
Anyone have a similar problem? Any help would be appreciated.
-- Mike Moulton
I've also the same kind of problem after upgrading from 6.3-eval to 7.0-pro
and after a fresh install. It's on a K6-3 400 64Mb. I can't find the source
of this problem (gcc, glibc, ...). Thankfully this does not occur on an
Athlon 600.
Help will be very welcome...
--
Jean-François Bocquet
* Mike Moulton (mike@meltmedia.com) [20001012 07:46]:
gcc gives the following error randomly throughout compile time. I am able to start the build again and it will continue past the last stop point and randomly stop again.
It would be a compiler problem if it would repeatedly fail at the same place. If not, I'd suspect flaky hardware.
The following occurred while compiling kernel 2.4.0-test7:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=k6 -fno-strict-aliasing -c -o prints.o prints.c prints.c: In function `sprintf_le_key': prints.c:90: Internal compiler error in `find_basic_blocks_1', at flow.c:732 Please submit a full bug report. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. cpp: output pipe has been closed
This problem is repeatable with any program that need to be compiled. I have tried the stock 7.0 install, as well as upgrading libc to 2.1.3-154 with no luck.
Problems like these will never be solved by changing the library. And it
would only be repeatable if you used the same compiler flags for all
programs, the most prominent being the -march=k6 flag.
So question is, does the compiler fail reliably at the same point with the same
error? If yes, please compile just that file with the same options but add a
-save-temps to the options. Send me the resuling .i file together with the
output of 'gcc -v' and I'll see what I can do (a collegue of mine is one of
the main i386 gcc hackers).
But just to iterate, this only makes sense if the compiler repeatedly fails
at the same point with the same error message.
Philipp
--
Philipp Thomas
participants (3)
-
mike＠meltmedia.com -
pthomas＠suse.de -
tns01＠free.fr