Your original problem was probably because GCC was trying to build both a 32-bit and a 64-bit version, and it couldn't find all of the files it needed for the 32-bit version. You're probably better off not installing the compatibility files and configuring your GCC only to build a 64-bit version. We had a similar problem, and that fixed it for us. Off the top of my head, I can't remember the configuration options we used, but that should at least give you a direction to look in... Thanks, Lyle -----Original Message----- From: gcc-help-owner@xxxxxxxxxxx [mailto:gcc-help-owner@xxxxxxxxxxx] On Behalf Of Simeon Nifos Sent: Wednesday, March 02, 2005 4:52 AM To: gcc-help@xxxxxxxxxxx Subject: compiling gcc-3.4.3 on a AMD quad OPTERON I couldn't compile gcc-3.4.3 from scratch! I followed the same procedure I am following up for years. It stopped because it coulnd't find in my SuSE 9.2 tree the file crti.o which does exist in /usr/lib64. It couldn't find it though and the compilation stopped. That problem was solved when I installed gcc32 compatibility libraries from an FTP mirror of SuSE 9.2 x86_64. The compilation went on and I was very happy to see that I can compile c++ programs. I was not so happy though when I realized that those programs I compiled successfully didn't run because they couldn't load libstdc++.so.6. I could only run statically linked programs! So what can I do for that??? Thanks in advance! Simeon N. __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/
