Libtool声称在交叉编译期间不支持共享库

17

我正在尝试为运行busybox 1.13的ARM嵌入式设备构建expat (2.0.0) XML解析库,在执行./configure时,我遇到了以下错误:

checking if libtool supports shared libraries... no

我已经指定了gcc、g++、ar、ranlib、strip等工具,并且这些工具都被配置工具找到了。我正在Ubuntu 12.10上使用最新的libtool(目前版本为2.4.2),所以为什么它会说libtool不支持共享库呢?我的configure命令如下:

./configure --host=arm --enable-shared CC=arm-none-linux-gnueabi-gcc CXX=arm-none-linux-gnueabi-g++ AR=arm-none-linux-gnueabi-ar RANLIB=arm-none-linux-gnueabi-ranlib STRIP=arm-none-linux-gnueabi-strip

...并且调用的完整输出如下:

    configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking build system type... i686-pc-linux-gnu
checking host system type... arm-unknown-none
checking for arm-gcc... arm-none-linux-gnueabi-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-none-linux-gnueabi-gcc accepts -g... yes
checking for arm-none-linux-gnueabi-gcc option to accept ANSI C... none needed
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by arm-none-linux-gnueabi-gcc... /usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld
checking if the linker (/usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld) is GNU ld... yes
checking for /usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld option to reload object files... -r
checking for BSD-compatible nm... nm
checking whether ln -s works... yes
checking how to recognise dependent libraries... unknown
checking how to run the C preprocessor... arm-none-linux-gnueabi-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for arm-g++... arm-none-linux-gnueabi-g++
checking whether we are using the GNU C++ compiler... yes
checking whether arm-none-linux-gnueabi-g++ accepts -g... yes
checking how to run the C++ preprocessor... arm-none-linux-gnueabi-g++ -E
checking for arm-g77... no
checking for arm-f77... no
checking for arm-xlf... no
checking for arm-frt... no
checking for arm-pgf77... no
checking for arm-fort77... no
checking for arm-fl32... no
checking for arm-af77... no
checking for arm-f90... no
checking for arm-xlf90... no
checking for arm-pgf90... no
checking for arm-epcf90... no
checking for arm-f95... no
checking for arm-fort... no
checking for arm-xlf95... no
checking for arm-ifc... no
checking for arm-efc... no
checking for arm-pgf95... no
checking for arm-lf95... no
checking for arm-gfortran... no
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse nm output from arm-none-linux-gnueabi-gcc object... ok
checking for objdir... .libs
checking for arm-ar... arm-none-linux-gnueabi-ar
checking for arm-ranlib... arm-none-linux-gnueabi-ranlib
checking for arm-strip... arm-none-linux-gnueabi-strip
checking if arm-none-linux-gnueabi-gcc supports -fno-rtti -fno-exceptions... no
checking for arm-none-linux-gnueabi-gcc option to produce PIC... -fPIC
checking if arm-none-linux-gnueabi-gcc PIC flag -fPIC works... yes
checking if arm-none-linux-gnueabi-gcc static flag -static works... yes
checking if arm-none-linux-gnueabi-gcc supports -c -o file.o... yes
checking whether the arm-none-linux-gnueabi-gcc linker (/usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by arm-none-linux-gnueabi-g++... /usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld
checking if the linker (/usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld) is GNU ld... yes
checking whether the arm-none-linux-gnueabi-g++ linker (/usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld) supports shared libraries... no
checking for arm-none-linux-gnueabi-g++ option to produce PIC... -fPIC
checking if arm-none-linux-gnueabi-g++ PIC flag -fPIC works... yes
checking if arm-none-linux-gnueabi-g++ static flag -static works... yes
checking if arm-none-linux-gnueabi-g++ supports -c -o file.o... yes
checking whether the arm-none-linux-gnueabi-g++ linker (/usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld) supports shared libraries... no
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for arm-gcc... (cached) arm-none-linux-gnueabi-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether arm-none-linux-gnueabi-gcc accepts -g... (cached) yes
checking for arm-none-linux-gnueabi-gcc option to accept ANSI C... (cached) none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking whether gcc accepts -fexceptions... yes
checking for ANSI C header files... (cached) yes
checking whether byte ordering is bigendian... no
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for memmove... yes
checking for bcopy... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking for off_t... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... no
checking for an ANSI C99-conforming __func__... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating expat_config.h
amarshall3@pg-oj-amarshall3:~/Sandbox/expat-2.0.0$ make
/bin/bash ./libtool --silent --mode=compile arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o lib/xmlparse.lo -c lib/xmlparse.c
/bin/bash ./libtool --silent --mode=compile arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o lib/xmltok.lo -c lib/xmltok.c
/bin/bash ./libtool --silent --mode=compile arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o lib/xmlrole.lo -c lib/xmlrole.c
/bin/bash ./libtool --silent --mode=link arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -no-undefined -version-info 6:0:5 -rpath /usr/local/lib  -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo
arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o xmlwf/xmlwf.o -c xmlwf/xmlwf.c
arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o xmlwf/xmlfile.o -c xmlwf/xmlfile.c
arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o xmlwf/codepage.o -c xmlwf/codepage.c
arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -o xmlwf/readfilemap.o -c xmlwf/readfilemap.c
xmlwf/readfilemap.c: In function 'filemap':
xmlwf/readfilemap.c:65: warning: implicit declaration of function 'read'
xmlwf/readfilemap.c:69: warning: implicit declaration of function 'close'
/bin/bash ./libtool --silent --mode=link arm-none-linux-gnueabi-gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H    -o xmlwf/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o libexpat.la

有人可以向我解释一下configure如何确定libtool是否支持构建共享库吗?

你不使用2.0.1有什么特别的原因吗?据我所知,手动构建expat也相当容易,你需要lib/xmlparse.c、lib/xmlrole.c和lib/xmltok.c。你可以使用mmap和-DUSE_MMAP...也许还需要从其他地方复制expat_config.h :) - auselen
我会继续使用2.0.0(至少目前是这样),因为我正在从一个基于Linux的嵌入式系统迁移到另一个不同架构的系统,并且我想尽量减少对我的代码的更改。我正在尝试同时为两个平台实现交叉编译,以便我只需修改单个代码库即可适用于两个平台。 - Alex Marshall
2个回答

28

从输出结果看:

检查构建系统类型... i686-pc-linux-gnu
检查主机系统类型... arm-unknown-none
...
检查arm-none-linux-gnueabi-gcc链接器(/usr/local/arm/arm-2007q1/arm-none-linux-gnueabi/bin/ld)是否支持共享库... 是
...
检查libtool是否支持共享库... 否
检查是否要构建共享库... 否
检查是否要构建静态库... 是

可能是因为--host=arm标志让libtool感到困惑,对于libtool来说它与--host=arm-unknown-none是一样的。尝试使用--host=arm-none-linux代替。我记得arm-unknown-none被用于那些想要为MCUs和其他嵌入式板做非RTOS(主循环)类型的项目,这些系统没有操作系统,一切都被静态地链接成一个映像。你的工具链是为Linux构建的:arm-none-linux


1
感谢您的答案,它拯救了我的理智。如果我需要为不同的平台进行交叉编译,--host 参数的语法是否有文档记录? - Cuadue
2
@Cuadue,有关target triplets的文档。随tarball一起提供的config.sub文件是该tarball的“权威”列表(直到它与更高版本的autotools打包)。最有用的信息将来自于编译器前缀(和其他binutils)的命名方式(在本例中为arm-none-linux-gnueabi-)。 - ldav1s

0
如果您使用Homebrew作为软件包管理器,请注意,某些公式是从编译为32位的瓶子中倒出来的,以最低公共分母为准。您可以通过使用以下命令将libtool重建为本机架构: $ brew install --build-from-source libtool
或者只需传递任何有效标志即可: $ brew install --universal libtool
大多数公式都有--universal标志,将生成i386和x86_64架构。

类似的例子请参考http://flummox-engineering.blogspot.com/2013/12/error-compiling-crosstool-ng-on-os-x.html。 - user3710680

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接