How about "forcing" it by the following ? It seems to work for hello-world with -m32 ; is there a large problem waiting to happen ? up2date --get glibc-devel-2.3.4-2.25.i386.rpm rpm -ivh glibc-devel-2.3.4-2.25.i386.rpm ]$ cc -m32 -o hello hello.c ]$ ./hello Hello, world! Thanks, Robert ( waiting for the gcc-4.2 build to get to the point where it fails/doesn't fail) > -----Original Message----- > From: Tim Prince [mailto:tprince@xxxxxxxxxxxxx] > Sent: 21 February 2007 14:51 > To: Atwood, Robert C > Cc: gcc-help@xxxxxxxxxxx > Subject: Re: Compiling gcc 4.2 prerelease on RedHat EL4 x86-64 > > Atwood, Robert C wrote: > > It's RedHat EL4 on a AMD > > x86-64 system, I've got all the gcc- and gcc4- packages that the > > installation system provides, installed. > > > > > > Then it fails to build due to > > /usr/bin/ld: crti.o: No such file: No such file or directory > > > > In this case, it is missing the 32-bit version of crti.o. > However, it > > seems like RedHat's installation system will not give me > the option to > > install the 32 bit version. > > > In addition to the (64-bit) gcc development package, you > would require > the Red Hat installation groups "legacy" (32-bit) development, and > "compatibility" (32-bit) libraries. In my experience, you would also > need to build and install the current gnu binutils source release, to > permit correct linking of libstdc++, not to mention updating > to current > gmp and mpfr. > BTW, there is a big difference among EL4 updates. If you have a dual > socket dual core system, you would likely find U4 useful; > otherwise U3 > may be sufficient. I don't think any of them have a > satisfactory gcc4. >
