I am trying to cross compile with libtool and I am getting
these really strange errors because libtool seems to want
to use cc no matter what.
(this is a snip from config.log)
...
configure:1490: checking dependency style of i386-mingw32msvc-gcc
configure:1526: result: gcc
configure:1539: checking for ld used by GCC
configure:1601: result:
/usr/local/project/install/Xmingwin/i386-mingw32msvc/bin/ld
...
ltconfig:1364: i386-mingw32msvc-gcc -o conftest -g -O2 -fno-builtin
-fno-rtti -fno-excep
tions conftest.c conftstm.o 1>&5
ltconfig:670:checking for cc option to produce PIC
ltconfig:679:checking that cc PIC flag -DDLL_EXPORT works.
ltconfig:689: cc -c -DDLL_EXPORT -DPIC conftest.java 1>&5
cc: conftest.java: linker input file unused since linking not done
ltconfig:741: checking if cc static flag -static works
ltconfig:750: cc -o conftest -static conftest.java 1>&5
/usr/bin/ld:conftest.java: file format not recognized; treating as linker
script
/usr/bin/ld:conftest.java:1: parse error
collect2: ld returned 1 exit status
ltconfig:787: checking if cc supports -c -o file.o
Does anyone know why libtool still tries to use cc? Is there
some reason behind this or it is just that nobody uses libtool
to cross compile?
Mo DeJong
Red Hat Inc
