Successful build/install of gcc-4.1.2 on Solaris10
The previous version of GCC used for the build was 3.4.6
I just built the compiler until I worked around the toolchain
problems: downrev gawk and missing gmp (watch 32 vs 64 bit) and mpfr.
Then a reconfig for everything built and installed in /usr
Hello all,
Several years ago in the gcc 3.3 time frame I looked into building cross
compilers using the current versions of gcc, glibc etc. for a number of
different systems. I quickly found that it was a quagmire. I inquired
of this list at that time and was told that the glibc hack was
pr
Andrew Pinski wrote:
On 8/17/07, Stephen M. Kenton <[EMAIL PROTECTED]> wrote:
Cross compiling works for me out of the box if done correctly. Yes I
have to compile GCC and glibc (or newlib) twice but I don't care as it
is all scripted.
Thanks,
Andrew Pinski
Great! Scripting is wo
During the recent discussion about cross compilers I was told "bugs
happen", so I went hunting.
I have been digging into why building a cross compiler dies in different
ways for different targets.
As seen below, the Linux targets which use glibc define
MD_UNWIND_SUPPORT and have
a customized lin
David Daney wrote:
You never state what you are trying to build. "cross compiler" does
not really narrow it down.
Also you don't state what errors you are experiencing.
I'm experimenting with building a Linux based cross compiler/tool-chain
for building the Kernel and Apps
for every target in
Can anyone explain why LIMITS_H_TEST is defined in cris/t-linux, while
it is not defined for any other linux target? It's a relatively recent
change. "ChangeLog-2005" line 5810 says
"2005-10-12 Hans-Peter Nilsson <[EMAIL PROTECTED]> config/cris/t-linux
(LIMITS_H_TEST): Define."
It breaks
Ian Lance Taylor wrote:
Steve Kenton <[EMAIL PROTECTED]> writes:
Is it ever possible to build libmudflap, libssp, or libgomp when
inhibit_libc is set?
It seems unlikely.
OK, then I'll pursue this idea
If not, is is reasonable to add a check to the top level configure to detect
I'm working on a patch to the top level configure to detect if inhibit_libc
will set for gcc and to avoid trying to build certain libraries in that
case.
I started to just clone the inhibit_libc logic from the gcc/configure,
but as
Ian commented, it is a bit strange. Then I realized that build-
