Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 335 subscribers
  • Views 504 views
  • Users 0 members are here
Related

Cross compiling with arm-xilinx-eabi-gcc

Former Member

I'm trying to compile the GSL library (GNU Scientific Library) for use on a Zedboard using Cygwin, and I am at a loss for how to resolve an error produced when invoking 'make'. Between each attempt I run 'make clean'. Perhaps someone can offer some insight.


In Windows 7 x64 using Cygwin terminal:

$ export PATH=$PATH:"/cygdrive/C/Xilinx/14.2/ISE_DS/EDK/gnu/arm/nt64/bin"

$ ./configure -host=arm-xilinx-eabi CC=arm-xilinx-eabi-gcc
[output omitted]

$ make
make  all-recursive
make[1]: Entering directory `/cygdrive/e/working/gsl-1.8'
Making all in gsl
make[2]: Entering directory `/cygdrive/e/working/gsl-1.8/gsl'
rm -f gsl*.h
HEADERLIST="../gsl*.h ../*/gsl*.h";
for h in $HEADERLIST; do
  BASENAME=`basename $h`;
  test -r $BASENAME || ln -s $h $BASENAME;
done
make[2]: Leaving directory `/cygdrive/e/working/gsl-1.8/gsl'
Making all in utils
make[2]: Entering directory `/cygdrive/e/working/gsl-1.8/utils'
/bin/sh ../libtool --tag=CC --mode=compile arm-xilinx-eabi-gcc -DHAVE_CONFIG_H  -I. -I. -I..      -g -O2 -c -o placeholder.lo placeholder.c
arm-xilinx-eabi-gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c placeholder.c -o placeholder.o
arm-xilinx-eabi-gcc -DHAVE_CONFIG_H -I. -I. -I..      -g -O2 -c strdup.c
/bin/sh ../libtool --tag=CC --mode=link arm-xilinx-eabi-gcc  -g -O2    -o libutils.la   placeholder.lo strdup.o  -lm
mkdir .libs
cygwin warning:
  MS-DOS style path detected: c:/xilinx/14.2/ise_ds/edk/gnu/arm/nt64/bin/../lib/gcc//libm.la
  Preferred POSIX equivalent is: /cygdrive/c/xilinx/14.2/ise_ds/edk/gnu/arm/nt64/lib/gcc/libm.la
  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
  Consult the user's guide for more details about POSIX paths:
    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
libtool: link: cannot build libtool library `libutils.la' from non-libtool objects on this host: strdup.o
Makefile:225: recipe for target `libutils.la' failed
make[2]: *** [libutils.la] Error 1
make[2]: Leaving directory `/cygdrive/e/working/gsl-1.8/utils'
Makefile:502: recipe for target `all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/cygdrive/e/working/gsl-1.8'
Makefile:274: recipe for target `all' failed
make: *** [all] Error 2

Thanks.

  • 0

    Hi, I've been trying to solve this same issue. It seems like ./configure does not believe there is an implementation of strdup available for this target, so it goes to compile the version provided with the GSL package.

    This seems to be normal, but for some reason, utils/strdup.c is being compiled as a normal .o which libtools then refuses to consume.

    I randomly tried deleting all references to strdup.c, strdup.o in the root Makefile to keep it from compiling it. This allows me to pass that specific error, but then after a few mins of compilation I get these kinds of linker errors:

    /remote/Xilinx/14.6/EDK/gnu/arm/lin/bin/../lib/gcc/arm-xilinx-eabi/4.7.2/../../../../arm-xilinx-eabi/bin/ld: warning: cannot find entry symbol _start; defaulting to 00008018
    /remote/Xilinx/14.6/EDK/gnu/arm/lin/bin/../lib/gcc/arm-xilinx-eabi/4.7.2/../../../../arm-xilinx-eabi/lib/libc.a(lib_a-abort.o): In function `abort':
    abort.c:(.text+0x10): undefined reference to `_exit'
    /remote/Xilinx/14.6/EDK/gnu/arm/lin/bin/../lib/gcc/arm-xilinx-eabi/4.7.2/../../../../arm-xilinx-eabi/lib/libc.a(lib_a-sbrkr.o): In function `_sbrk_r':
    sbrkr.c:(.text+0x1c): undefined reference to `_sbrk'
    /remote/Xilinx/14.6/EDK/gnu/arm/lin/bin/../lib/gcc/arm-xilinx-eabi/4.7.2/../../../../arm-xilinx-eabi/lib/libc.a(lib_a-signalr.o): In function `_kill_r':
    signalr.c:(.text+0x20): undefined reference to `_kill'
    /remote/Xilinx/14.6/EDK/gnu/arm/lin/bin/../lib/gcc/arm-xilinx-eabi/4.7.2/../../../../arm-xilinx-eabi/lib/libc.a(lib_a-signalr.o): In function `_getpid_r':
    signalr.c:(.text+0x3c): undefined reference to `_getpid'

    I was browsing through "libxil.a" from my SDK project using "nm -g" and it seems like these symbols might be defined inside? Are we supposed to link the GSL build and libxil.a together? Not sure how to proceed...