Re: gcc 4.2.0 compilation failing on x86_64 machine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ryan Propper wrote:
I'm trying to do the "x86_64-unknown-linux-gnu" build of gcc and g++
4.2.0.  The machine I'm working on is an Intel Pentium D, which
apparently supports both 32 and 64 bit architectures.  Although the
configuration succeeds, about halfway through the build step I get
this:

/tmp/foo/objdir/./gcc/xgcc -B/tmp/foo/objdir/./gcc/  -O2 -O2 -g -O2
-DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition  -isystem ./include  -I.
-I32 -I../../gcc-4.2.0 /gcc -I../../gcc-4.2.0/gcc/32
-I../../gcc-4.2.0/gcc/../include
-I../../gcc-4.2.0/gcc/../libcpp/include
-I../../gcc-4.2.0/gcc/../libdecnumber -I../libdecnumber -m32 -g0
The '-m32' means this happening when producing the 32-bit startup...
In file included from /usr/include/features.h:342,
                from /usr/include/stdio.h:28,
                from ../../gcc- 4.2.0/gcc/tsystem.h:90,
                from ../../gcc-4.2.0/gcc/crtstuff.c:68:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory

In /usr/include/gnu there is a stubs-64.h and a stubs.h, but no
stubs-32.h.  Is there some flag that I need to be passing at the
configuration or make step to make it see stubs-64 instead?
If there are the two required glibcs for 64-bit and 32-bit, then most probably is that header for the 32-bit production.... The 'gnu/stubs.h' for SuSE 10.1 is :

Dell:/opt # cat host-SuSE10.1_x86_64/usr/include/gnu/stubs.h
/* This file selects the right generated file of `__stub_FUNCTION' macros
  based on the architecture being compiled for.  */

#include <bits/wordsize.h>

#if __WORDSIZE == 32
# include <gnu/stubs-32.h>
#elif __WORDSIZE == 64
# include <gnu/stubs-64.h>
#else
# error "unexpected value for __WORDSIZE macro"
#endif

What does your one tell? Maybe you haven't installed any C-library support
for 32-bit ?

What is your x86_64 platform and why there isn't that support for 'bi-arch'
code production just as GCC expects there being ?


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux