veekays / iphonedevonlinux

Automatically exported from code.google.com/p/iphonedevonlinux
0 stars 0 forks source link

Cannot Build on Ubuntu 10.10 with libstdc++ failure. #34

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Build on Ubuntu 10.10
2.
3.

What is the expected output? What do you see instead?
Build. Non-Build.

What version of the product are you using? On what operating system?

Please provide any additional information below.

gcc  -Wall -Wno-long-double -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1 
-DDEBUG -DLD_CLASSIC="\"arm-apple-darwin9-ld_classic\""  -I. 
-I/home/michael/Linux-Stored-Projects/toolchain/toolchain/src/cctools/ld64 
-I/home/michael/Linux-Stored-Projects/toolchain/toolchain/src/cctools/ld64/src 
-I../include 
-I/home/michael/Linux-Stored-Projects/toolchain/toolchain/src/cctools/include 
-include 
/home/michael/Linux-Stored-Projects/toolchain/toolchain/src/cctools/include/exte
rn.h 
-I/home/michael/Linux-Stored-Projects/toolchain/toolchain/src/cctools/include/fo
reign -m32 -fno-builtin-round -fno-builtin-trunc -g -O2   -c -o strlcpy.o 
/home/michael/Linux-Stored-Projects/toolchain/toolchain/src/cctools/ld64/src/str
lcpy.c
g++ -o ld64 ld.o Options.o debugline.o strlcpy.o -m32 -L../libstuff -lstuff 
-luuid -lcrypto -ldl
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/libstdc++.a when searching for -lstdc++
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status
make[1]: *** [ld64] Error 1
make[1]: Leaving directory 
`/home/michael/Linux-Stored-Projects/toolchain/toolchain/bld/cctools-iphone/ld64
'
make: *** [ld64] Error 2

Original issue reported on code.google.com by mcoll...@gmail.com on 10 Jan 2011 at 4:29