OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: g33k on February 17, 2005, 10:55:33 am

Title: "c Compiler Cannot Create Executable"
Post by: g33k on February 17, 2005, 10:55:33 am

When cross-compiling (actually, when running the configure script), I sometimes get an error that says "C Compiler Cannot Create Executable". Does anyone else get this? What does it mean? How do I fix it?

Thanks!

Title: "c Compiler Cannot Create Executable"
Post by: scogan on February 17, 2005, 11:12:47 am

I get this from certain configure scripts as well. Here's a slice of config.log:

Code: [Select]

configure:588: checking host system type
configure:613: checking for gcc
configure:726: checking whether the C compiler (armv5tel-linux-gcc -O2 -Wall -Wl
,-rpath-link,/opt/arm/3.3.2-vfp/armv5tel-cacko-linux/X11R6/lib) works
configure:742: armv5tel-linux-gcc -o conftest -O2 -Wall  -Wl,-rpath-link,/opt/ar
m/3.3.2-vfp/armv5tel-cacko-linux/X11R6/lib conftest.c  1>&5
configure:739: warning: return type defaults to `int'
/opt/arm/3.3.2-vfp/lib/gcc-lib/armv5tel-cacko-linux/3.3.2/collect2: /lib/libc.so
.6: version `GLIBC_2.3' not found (required by /opt/arm/3.3.2-vfp/lib/gcc-lib/ar
mv5tel-cacko-linux/3.3.2/collect2)
configure: failed program was:

#line 737 "configure"
#include "confdefs.h"

main(){return(0);}
Is this an issue with  my environment possibly?  I get this error both with the native and zgcc images on the z, and with the SDK on a  Debian sarge box.

Thank you

Title: "c Compiler Cannot Create Executable"
Post by: Mickeyl on February 17, 2005, 11:20:12 am

Sounds like either your toolchain should be compiled with other standard include directories or you should supply some more CFLAGS pointing to where your proper libc.so is.

Title: "c Compiler Cannot Create Executable"
Post by: scogan on February 17, 2005, 11:55:21 am

sh-2.05a# strings `which armv5tel-linux-gcc` |grep GLIBC
GLIBC_2.1
GLIBC_2.0

What weirds me out here is that gcc and collect2 seem to be linked against different glibc versions.

sh-2.05a# strings /opt/arm/3.3.2-vfp/lib/gcc-lib/armv5tel-cacko-linux/3.3.2/collect2 |grep GLIBC
GLIBC_2.3
GLIBC_2.1
GLIBC_2.0

I have  glibc 2.2.5 on the debian system in question. On my slackware boxes I have 2.2.4 and 2.1.3. I guess technically I could upgrade, but I have to think that I've done something horribly wrong as I would expect different results with the zgcc.img. I'm fairly sure that others are using it with no problems.

What madness have I perpetrated?