LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux From Scratch
User Name
Password
Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.

Notices

Reply
 
Search this Thread
Old 11-09-2007, 04:01 AM   #1
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Rep: Reputation: 0
GCC 4.1.2 failing to compile


Code:
CC=" stage1/xgcc -Bstage1/ -B/tools/x86_64-unknown-linux-gnu/bin/" CC_FOR_BUILD=" stage1/xgcc -Bstage1/ -B/tools/x86_64-unknown-linux-gnu/bin/" \
                 STAGE_PREFIX=stage1/ \
                 ADAFLAGS="" CFLAGS="-g -O2" LDFLAGS="" WARN_CFLAGS="\$(GCC_WARN_CFLAGS)" STRICT_WARN="-pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute " libdir=/tools/lib LANGUAGES="c gcov gcov-dump " MAKEINFO="makeinfo --split-size=5000000" MAKEINFOFLAGS="--no-split" MAKEOVERRIDES= OUTPUT_OPTION="-o \$@" \
                 CFLAGS="-g -O2" WERROR="" 
make[2]: Entering directory `/mnt/lfs/sources/gcc-build/gcc'
stage1/xgcc -Bstage1/ -B/tools/x86_64-unknown-linux-gnu/bin/   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute     -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include     -c insn-attrtab.c \
          -o insn-attrtab.o
../../gcc-4.1.2/gcc/config/i386/i386.md: In function 'internal_dfa_insn_code':
../../gcc-4.1.2/gcc/config/i386/i386.md:200: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [insn-attrtab.o] Error 1
make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/mnt/lfs/sources/gcc-build/gcc'
It never makes it past this part no matter how I go about getting there. I have searched google and there is absolutely no information thats relevant to me about how to fix this problem.

Can anyone point me in a direction, preferably the right one?
 
Old 11-10-2007, 09:24 AM   #2
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
I will post up more info if anyone needs it.


I was using the live CD when I got this error. The funny part about this is no matter which HOST system I use or which ever version of the CD/Book I use I can never EVER complete the gcc build. I always fail on the GCC build. Can someone for the love of whatever, fix my problem???


I am now getting frustrated with this whole process because there is no information gcc compile errors.

Only thing google tells me is, its a hardware issue. Well, I beg to differ, because all this hardware has been proven to work perfectly since I hand picked it 2 months ago.

Last edited by havenoidea; 11-10-2007 at 09:25 AM.
 
Old 11-10-2007, 09:41 AM   #3
Seph64
Member
 
Registered: Feb 2003
Distribution: Gentoo, FreeBSD, LFS
Posts: 298
Blog Entries: 21

Rep: Reputation: 30
Saying that you have proven your hardware to work perfectly since you hand picked it is a cop-out. What have you actually done to prove that your hardware was not at fault? Did you check your CPU temps while you were compiling?
 
Old 11-10-2007, 05:50 PM   #4
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Seph64 View Post
Saying that you have proven your hardware to work perfectly since you hand picked it is a cop-out. What have you actually done to prove that your hardware was not at fault? Did you check your CPU temps while you were compiling?

temps are 36C CPU and 26C MOBOPU and I memtested the memory 2 hours with NO errors. Now do you wanna tell me again that I cop'd out?

thanks for at least having an opinion. Now what the hell can this be?
 
Old 11-10-2007, 05:52 PM   #5
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
I also just got done checking the memory 30 minutes ago. My test are done and up to date, my system works perfectly.
 
Old 11-10-2007, 06:44 PM   #6
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Some new info this time, I actually got it to tell me something new.
Code:
/bin/sh ../../gcc-4.1.1/gcc/../move-if-change tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
gcc   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.1/gcc -I../../gcc-4.1.1/gcc/. -I../../gcc-4.1.1/gcc/../include -I../../gcc-4.1.1/gcc/../libcpp/include     -c insn-attrtab.c \
          -o insn-attrtab.o
../../gcc-4.1.1/gcc/config/i386/i386.md: In function 'internal_dfa_insn_code':
../../gcc-4.1.1/gcc/config/i386/i386.md:200: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
*** glibc detected *** /usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1: free(): invalid next size (normal): 0x0000000003d14e60 ***
======= Backtrace: =========
/lib/libc.so.6[0x2afe8f217b0a]
/lib/libc.so.6(cfree+0x8c)[0x2afe8f21b6fc]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6ecdaf]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x4eaa40]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56a672]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56b762]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56c227]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6f5506]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6f55fc]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6f560e]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x45da8a]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x40a728]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x7329a2]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x7338af]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x4101c6]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6d8e2f]
/lib/libc.so.6(__libc_start_main+0xf4)[0x2afe8f1c3b44]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1(calloc+0x189)[0x4026e9]
======= Memory map: ========
00400000-00958000 r-xp 00000000 08:01 1754702                            /usr/lib/gcc/x86_64-linux-gnu/4.1/cc1
00b57000-00b5e000 rw-p 00557000 08:01 1754702                            /usr/lib/gcc/x86_64-linux-gnu/4.1/cc1
00b5e000-04069000 rw-p 00b5e000 00:00 0                                  [heap]
2afe8ef88000-2afe8efa5000 r-xp 00000000 08:01 2102060                    /lib/ld-2.6.1.so
2afe8efa5000-2afe8efc9000 rw-p 2afe8efa5000 00:00 0 
2afe8efca000-2afe8f0da000 rw-p 2afe8efca000 00:00 0 
2afe8f1a4000-2afe8f1a6000 rw-p 0001c000 08:01 2102060                    /lib/ld-2.6.1.so
2afe8f1a6000-2afe8f2f8000 r-xp 00000000 08:01 2102063                    /lib/libc-2.6.1.so
2afe8f2f8000-2afe8f4f7000 ---p 00152000 08:01 2102063                    /lib/libc-2.6.1.so
2afe8f4f7000-2afe8f4fa000 r--p 00151000 08:01 2102063                    /lib/libc-2.6.1.so
2afe8f4fa000-2afe8f4fc000 rw-p 00154000 08:01 2102063                    /lib/libc-2.6.1.so
2afe8f4fc000-2afe8f802000 rw-p 2afe8f4fc000 00:00 0 
2afe8f8b5000-2afe90176000 rw-p 2afe8f8b5000 00:00 0 
2afe901b7000-2afe907b7000 rw-p 2afe901b7000 00:00 0 
2afe907e6000-2afe916e8000 rw-p 2afe907e6000 00:00 0 
2afe916e8000-2afe91747000 rw-p 2afe907b7000 00:00 0 
2afe91747000-2afe946a7000 rw-p 2afe91747000 00:00 0 
2afe946a8000-2afea0767000 rw-p 2afe946a8000 00:00 0 
2afea0779000-2afea0786000 r-xp 00000000 08:01 2097166                    /lib/libgcc_s.so.1
2afea0786000-2afea0986000 ---p 0000d000 08:01 2097166                    /lib/libgcc_s.so.1
2afea0986000-2afea0987000 rw-p 0000d000 08:01 2097166                    /lib/libgcc_s.so.1
2afea4000000-2afea4021000 rw-p 2afea4000000 00:00 0 
2afea4021000-2afea8000000 ---p 2afea4021000 00:00 0 
7fff1bb03000-7fff1bb22000 rw-p 7fff1bb03000 00:00 0                      [stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vdso]
The bug is not reproducible, so it is likely a hardware or OS problem.
make[1]: *** [insn-attrtab.o] Error 1
make[1]: Leaving directory `/mnt/clfs/sources/gcc-build/gcc'
make: *** [all-gcc] Error 2

keeps forcing me to a hardware problem, but the bios is set by SPD. Memtest86 comes back clean as a whistle and everything else I have ever tried works on this system except for this compiling GCC error.

I am even using the generic ubuntu kernel for 64 bit. Beyond using a new computer I can't really change much... This is so frustrating yet so sad...
 
Old 11-10-2007, 07:29 PM   #7
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
again...

Code:
/bin/sh ../../gcc-4.1.1/gcc/../move-if-change tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
gcc   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.1/gcc -I../../gcc-4.1.1/gcc/. -I../../gcc-4.1.1/gcc/../include -I../../gcc-4.1.1/gcc/../libcpp/include     -c insn-attrtab.c \
          -o insn-attrtab.o
*** glibc detected *** /usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1: corrupted double-linked list: 0x0000000003950270 ***
======= Backtrace: =========
/lib/libc.so.6[0x2adb01cbadec]
/lib/libc.so.6(__libc_malloc+0x93)[0x2adb01cbbe23]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x7e6758]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6ecc5b]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x4eb8a5]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56a613]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56b762]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56c227]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6f5506]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6f55fc]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6f560e]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x45da8a]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x40a728]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x7329a2]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x7338af]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x4101c6]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x6d8e2f]
/lib/libc.so.6(__libc_start_main+0xf4)[0x2adb01c65b44]
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1(calloc+0x189)[0x4026e9]
======= Memory map: ========
00400000-00958000 r-xp 00000000 08:01 1754702                            /usr/lib/gcc/x86_64-linux-gnu/4.1/cc1
00b57000-00b5e000 rw-p 00557000 08:01 1754702                            /usr/lib/gcc/x86_64-linux-gnu/4.1/cc1
00b5e000-04062000 rw-p 00b5e000 00:00 0                                  [heap]
2adb01a2a000-2adb01a47000 r-xp 00000000 08:01 2102060                    /lib/ld-2.6.1.so
2adb01a47000-2adb01a6b000 rw-p 2adb01a47000 00:00 0 
2adb01a6c000-2adb01b7c000 rw-p 2adb01a6c000 00:00 0 
2adb01c46000-2adb01c48000 rw-p 0001c000 08:01 2102060                    /lib/ld-2.6.1.so
2adb01c48000-2adb01d9a000 r-xp 00000000 08:01 2102063                    /lib/libc-2.6.1.so
2adb01d9a000-2adb01f99000 ---p 00152000 08:01 2102063                    /lib/libc-2.6.1.so
2adb01f99000-2adb01f9c000 r--p 00151000 08:01 2102063                    /lib/libc-2.6.1.so
2adb01f9c000-2adb01f9e000 rw-p 00154000 08:01 2102063                    /lib/libc-2.6.1.so
2adb01f9e000-2adb022a4000 rw-p 2adb01f9e000 00:00 0 
2adb02357000-2adb02c18000 rw-p 2adb02357000 00:00 0 
2adb02c59000-2adb03259000 rw-p 2adb02c59000 00:00 0 
2adb03288000-2adb0418a000 rw-p 2adb03288000 00:00 0 
2adb0418a000-2adb041e9000 rw-p 2adb03259000 00:00 0 
2adb041e9000-2adb07149000 rw-p 2adb041e9000 00:00 0 
2adb0714a000-2adb13209000 rw-p 2adb0714a000 00:00 0 
2adb1321b000-2adb13228000 r-xp 00000000 08:01 2097166                    /lib/libgcc_s.so.1
2adb13228000-2adb13428000 ---p 0000d000 08:01 2097166                    /lib/libgcc_s.so.1
2adb13428000-2adb13429000 rw-p 0000d000 08:01 2097166                    /lib/libgcc_s.so.1
2adb14000000-2adb14021000 rw-p 2adb14000000 00:00 0 
2adb14021000-2adb18000000 ---p 2adb14021000 00:00 0 
7fffa9060000-7fffa9080000 rw-p 7fffa9060000 00:00 0                      [stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vdso]
../../gcc-4.1.1/gcc/config/i386/i386.md: In function 'internal_dfa_insn_code':
../../gcc-4.1.1/gcc/config/i386/i386.md:200: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[1]: *** [insn-attrtab.o] Error 1
make[1]: Leaving directory `/mnt/clfs/sources/gcc-build/gcc'
make: *** [all-gcc] Error 2
so I went a step further and increased the memory timings slower then what they are stock settings. I still get this error.

I see this error may be due to NF4 chipset, I wonder if getting a new bios firmware update will help?
 
Old 11-10-2007, 07:29 PM   #8
gerald_M2B
Member
 
Registered: Oct 2007
Posts: 34

Rep: Reputation: 15
In your results, this line brought back some memories of my own, compiling gcc ? version:
/bin/sh ../../gcc-4.1.1/gcc/../move-if-change tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
This is a loop in the source code, which passes over the section three times.
I eventually picked up and got through to the finish line. Took two continuations
after the failed start. Sorry, I do not remember what changes I made, but I had
to add two links to make it work.

One thing I noticed about your most recent post was that it appears that different
gcc versions are being amalgumated into one pool. I think you need to find a way
to use only the same compiler version to work your way over the source.

From your backtrace, 4.1.3:
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56b762]
From your command line reproduced in the second line above: 4.1.1
Do not expect to succeed with mixed versions of the compiler.

Gerald
 
Old 11-10-2007, 09:55 PM   #9
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
One thing I noticed about your most recent post was that it appears that different
gcc versions are being amalgumated into one pool. I think you need to find a way
to use only the same compiler version to work your way over the source.
I'd like to know as well, because from what I can tell I didn't install no 4.1.3. I have 4.1.1 d/l'd and thats what I am trying to install as my compiler for compiling LFS, but my host system uses gcc 4.1.2.

4.1.3 seems odd indeed, because I am not sure where its coming from???

This is really frustrating, I am completely stumped. I have checked my memory without failure, I have just updated the newest bios version thinking my NF4 chipset was the problem(still may be, but firmware is up to date)but thats updated now as well and I still get the same error.

I am wondering now if I should just start over and re-compile binutils, its the only thing I compiled and the only thing I compiled with the old bios settings and bios firmware. I am no guru I don't even know if this will work???


edit: compiled again this time with no backtrace, sorta like the first post. Just weird how each time it has a different way of erroring but still with the same error. Sounds hardware, but what sort of problem because everything else seems to have no problems running on this machine. I even installed and compiled gcc-4.1.1 with the minimal gentoo liveCD.

Just shoot me now.

Last edited by havenoidea; 11-10-2007 at 09:58 PM.
 
Old 11-10-2007, 10:55 PM   #10
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56b762]

I don't even have anything in /usr/lib/gcc/x86_64-linux-gnu its empty, zero items????? so what is that????

after following some more advice, repeatedly just trying to make all-gcc and now this pops up.

Code:
gcc   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.1/gcc -I../../gcc-4.1.1/gcc/. -I../../gcc-4.1.1/gcc/../include -I../../gcc-4.1.1/gcc/../libcpp/include     -c insn-attrtab.c \
          -o insn-attrtab.o
../../gcc-4.1.1/gcc/config/i386/i386.md:192:9: warning: null character(s) ignored
../../gcc-4.1.1/gcc/config/i386/i386.md: In function 'internal_dfa_insn_code':
../../gcc-4.1.1/gcc/config/i386/i386.md:192: error: 'retur' undeclared (first use in this function)
../../gcc-4.1.1/gcc/config/i386/i386.md:192: error: (Each undeclared identifier is reported only once
../../gcc-4.1.1/gcc/config/i386/i386.md:192: error: for each function it appears in.)
../../gcc-4.1.1/gcc/config/i386/i386.md:192: error: expected ';' before numeric constant
../../gcc-4.1.1/gcc/config/i386/i386.md:192:25: warning: null character(s) ignored
../../gcc-4.1.1/gcc/config/i386/i386.md:193:1: warning: null character(s) ignored
../../gcc-4.1.1/gcc/config/i386/i386.md:194:2: error: invalid preprocessing directive #l
../../gcc-4.1.1/gcc/config/i386/i386.md:194:3: warning: null character(s) ignored
make[1]: *** [insn-attrtab.o] Error 1
make[1]: Leaving directory `/mnt/clfs/sources/gcc-build/gcc'
make: *** [all-gcc] Error 2
am I right to assume that this came up because one of the errors corrupted something in the config files?

Last edited by havenoidea; 11-10-2007 at 11:04 PM.
 
Old 11-14-2007, 04:02 AM   #11
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Code:
   ../../gcc/c-decl.c -o c-decl.o
/home/jasin/Desktop/build/gcc-4.2.2/gcc_x64/./prev-gcc/xgcc -B/home/jasin/Desktop/build/gcc-4.2.2/gcc_x64/./prev-gcc/ -B/usr/x86_64-linux-gnu/bin/ -c   -march=athlon64 -O2 -pipe -fomit-frame-pointer -fno-ident -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include  -I../../gcc/../libdecnumber -I../libdecnumber    ../../gcc/c-typeck.c -o c-typeck.o
../../gcc/c-typeck.c: In function ‘tagged_types_tu_compatible_p’:
../../gcc/c-typeck.c:1041: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [c-typeck.o] Error 1
make[3]: Leaving directory `/home/jasin/Desktop/build/gcc-4.2.2/gcc_x64/gcc'
make[2]: *** [all-stage3-gcc] Error 2
make[2]: Leaving directory `/home/jasin/Desktop/build/gcc-4.2.2/gcc_x64'
make[1]: *** [stage3-bubble] Error 2
make[1]: Leaving directory `/home/jasin/Desktop/build/gcc-4.2.2/gcc_x64'
make: *** [bootstrap] Error 2
I made it a little further by following a guide on ubuntu forums on compiling gcc 4.2.2 with optimized flags. Now I get this, but the good part is it right through the above part on both the 2 previous passes. This is very good news.

Now what does this mean ^^^^. I looked it up on google and it seems all i get is old patches because 'patch' just complains that it assume -R (reverse) but I said no and now none of the patches work.
 
Old 11-16-2007, 12:17 AM   #12
gerald_M2B
Member
 
Registered: Oct 2007
Posts: 34

Rep: Reputation: 15
For others to make good use of the forum, keep the discussion related to the subject title.
You started with gcc-4.1.2, but deviations from the topic do not aid others researching
problems. If you choose to use various compilers, use a more general title, or start
a different thread.
You mentioned patches that no longer work. The patches on the LFS book were for a
specific version, and not necessarily helpful for later compiler versions, as they need to
be checked against the ChangeLog and code to see if a similar patch was already made.
Readers would not know what patches you are using OR not using, so they may not
understand where you are at or going.

Gerald
 
Old 11-17-2007, 08:56 AM   #13
havenoidea
LQ Newbie
 
Registered: Nov 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Code:
You started with gcc-4.1.2, but deviations from the topic do not aid others researching
problems.

All u would have to do is read the thread and u will see why I wanted to try and compile 4.2.2, because nothing I did to 4.1.1 was working. If 4.2.2 compiled then it would have to be something else other then my pc. That was my consensus. Do you feel that was wrong?

Besides, the original error I was getting when compiling 4.1.1 was due to my CPU apparently because once I switched out the single core for the dual core processor 4.1.1 compiled easily with no errors anywhere. I was most shocked, 3 days worth of errors, I wasn't expecting a new dual core processor to make that much of a difference.

Now I would like someone to explain to me how that happens. Because essentially that means the processor I bought is bad. But the sad part is I been using it for quite some time so there is no warranty anymore, but yet it is clearly an inferior product.


sry I was so confusing, but as u can see (hardware) CPU was never mentioned by anyone as a result of this error. I was lucky enough to have another processor sitting here to try. No offense, but I don't see anyone with any good advice on this board.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
GCC in chroot failing to build, unable to find headers falt004 Linux From Scratch 4 08-03-2007 11:00 AM
gcc failing, ld seems to be the problem trigggl AIX 9 06-15-2007 02:22 PM
gcc compilation failing on UnixWare for LOCALE_ALIAS_PATH subu_s Programming 0 12-21-2004 08:15 AM
Compile 2.6.9 keeps failing. musicman_ace Suse/Novell 6 11-27-2004 05:16 AM
xfree compile failing et1ssgmiller Linux - Software 2 02-13-2003 08:43 AM


All times are GMT -5. The time now is 09:21 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration