bloudraak / mingw-and-ndk

Automatically exported from code.google.com/p/mingw-and-ndk
0 stars 0 forks source link

error building GCC "make all-target-libgcc #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. configure GCC for host=i686-apple-darwin11 build=x86_64-linux_gnu 
target=x86_64-w64-mingw32
1b. build and install gcc-c
2. build mingw-w64 crt
3. build "make all-target-libgcc"

What is the expected output? What do you see instead?
it should compile

What version of the product are you using? On what operating system?
http://code.google.com/p/mingw-and-ndk/downloads/detail?name=multiarch-darwin11-
cctools127.2-gcc42-5666.3-llvmgcc42-2336.1-Linux-120724.tar.xz&can=2&q=
on Debian stable.

The error is:
i686-apple-darwin11-gcc --sysroot /home/ruben/darwin/MacOSX10.7.sdk -c   -O2 
-march=nocona -mtune=core2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall 
-Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes 
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros 
-Wno-overlength-strings -Wold-style-definition -Wc++-compat   -DHAVE_CONFIG_H 
-I. -Ilto -I/home/ruben/mingw-w64/src/gcc/gcc 
-I/home/ruben/mingw-w64/src/gcc/gcc/lto 
-I/home/ruben/mingw-w64/src/gcc/gcc/../include 
-I/home/ruben/mingw-w64/src/gcc/gcc/../libcpp/include 
-I/home/ruben/mingw-w64/prereq/i686-apple-darwin11/install/include 
-I/home/ruben/mingw-w64/prereq/i686-apple-darwin11/install/include 
-I/home/ruben/mingw-w64/prereq/i686-apple-darwin11/install/include  
-I/home/ruben/mingw-w64/src/gcc/gcc/../libdecnumber 
-I/home/ruben/mingw-w64/src/gcc/gcc/../libdecnumber/bid -I../libdecnumber 
-I/home/ruben/mingw-w64/prereq/i686-apple-darwin11/install/include  
-I/home/ruben/mingw-w64/prereq/i686-apple-darwin11/install/include 
-DCLOOG_INT_GMP -DCLOOG_ORG 
-I/home/ruben/mingw-w64/prereq/i686-apple-darwin11/install/include 
/home/ruben/mingw-w64/src/gcc/gcc/lto/lto.c -o lto/lto.o
ld: warning: using ld_classic
can't exec ld_classic

Original issue reported on code.google.com by VanBoxem...@gmail.com on 16 Aug 2012 at 1:11