It is highly important to define CFLAGS='-m32' prior to running configure. Otherwise the gcc supplied with RHEL4 will try to compile 64bit binaries, and that is not welcome in your scenario.
Also, If you already have gcc-2.95.3 compiled and working on another machine installed in its own tree hierarchy (you said something about old Xeon machines?) just take the installation tree and copy it to your RHEL4 64bit machine, most likely that this will work and save you from compiling the compiler. - Noam On 11/26/06, Yedidyah Bar-David <[EMAIL PROTECTED]> wrote:
On Sun, Nov 26, 2006 at 08:42:39AM +0200, Michael Green wrote: > On 11/23/06, Ilya Konstantinov <[EMAIL PROTECTED]> wrote: > >On 11/23/06, Michael Green <[EMAIL PROTECTED]> wrote: > >> I'm trying to build old gcc-2.95.* on AMD x64 with RHEL4. > > > >Does such an old version of gcc even support x86-64 (as a target for > >the code it compiles, not as a target to run on)? > > Do you mean by that that it would be impossible to use gcc 2.9x on x64 > to compile our old code? We don't require the resulting binary to be > 64bit, 32bit is just fine. I do not think this should be a problem. Ilya commented on x86-64, meaning 64bit binaries. > > Problem is, we have old code here that doesn't compile with any gcc > higher than 2.95. Currenty the code runs on old Xeon 32bit based > cluster, and that hardware is running out of warrantly and is hassle > to maintain on OS level. We would be happy to migrate that code to > our newer cluster which is AMD x64/RHEL AS4. > > In the light of above what are my options? Porting the code to newer > gcc is not feasable. > > If not, try > >'configure' with --target=i686. > Gives: Perhaps 'i686-pc-linux-gnu'? -- Didi ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
