HI

I am using cross-compiler to build fd.io_odp4vpp for aarch64 target.

I succeeded to "make build",
However when I "make plugins",  it show below error,

Seems the problem in   
./build-root/build-armada-a8k_debug-aarch64/vpp-api/python/Makefile:    python 
setup.py build_ext -L $(prefix)/lib64 \
Why setup.py does not take cross compiler?  Would you kindly help me out?

==============error==========================

libtool: install: aarch64-linux-gnu-ranlib 
/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/install-armada-a8k_debug-aarch64/vpp-api/lib/libpneum.a
running build_ext
building 'vpp_api' extension
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
-Wall -Wstrict-prototypes -fPIC 
-I/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/install-armada-a8k_debug-aarch64/vpp-api/../vppinfra/include/
 -I/usr/include/python2.7 -c vpp_papi/pneum_wrap.c -o 
build/temp.linux-x86_64-2.7/vpp_papi/pneum_wrap.o
libtool: finish: 
PATH="/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/tools/ccache-bin:/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/tools/bin:/home/ericxh/bin:/home/ericxh/work/toolchain/marvell-gcc-5.2.1-16.02.0-armv8/armv8/le/aarch64v8-marvell-linux-gnu-5.2.1_i686_20151110/bin/:/home/ericxh/work/tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/sbin"
 ldconfig -n 
/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/install-armada-a8k_debug-aarch64/vpp-api/lib
----------------------------------------------------------------------
Libraries have been installed in:
   
/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/install-armada-a8k_debug-aarch64/vpp-api/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv 
-O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
build/temp.linux-x86_64-2.7/vpp_papi/pneum_wrap.o 
-L/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/install-armada-a8k_debug-aarch64/vpp-api/lib64
 -lpneum -o build/lib.linux-x86_64-2.7/vpp_api.so
/usr/bin/ld: cannot find -lpneum
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
make[5]: *** [install-exec-local] Error 1
make[5]: Leaving directory 
`/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/build-armada-a8k_debug-aarch64/vpp-api/python'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory 
`/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/build-armada-a8k_debug-aarch64/vpp-api/python'
make[3]: *** [install] Error 2
make[3]: Leaving directory 
`/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/build-armada-a8k_debug-aarch64/vpp-api/python'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory 
`/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root/build-armada-a8k_debug-aarch64/vpp-api'
make[1]: *** [vpp-api-install] Error 2
make[1]: Leaving directory 
`/mnt/disk1/ericxh/work/git_work/fd.io_odp4vpp/vpp/build-root'
make: *** [plugins] Error 2

Thanks
Eric


_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to