Cross Compilation of oprofile

amitk.gupta09 · 08-06-2012, 01:45 AM

I am trying to cross compile the oprofile.Detail related to cross compile is mentioned below :
Cross-Compiler -- arm-eglibc-linux-gnueabi-gcc
Build_cpu -- i686
Build_os -- linux-gnu
Host_cpu -- arm
Host_os -- linux-gnueabi
Oprofile Package Version -- oprofile-0.9.6

and i am executing below mentioned command --
$./configure --prefix=${INSTALL_PATH} --host=${TOOLCHAIN_PREFIX} --with-kernel-support --with-extra-libs=${ARM_TOOLCHAIN_PATH}/lib --with-extra-includes=${ROOTFS}/include CXX=arm-eglibc-linux-gnueabi-g++

Configuration successfully happened but when i am giving below mentioned command

$ make

i got this linking error message --
/usr/lib/libbfd.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status

I do not know why linker not getting the libbfd.so even though linker getting the other libraries from same directory,in which libbfd.so is also present. libbfd.so is softlink to libbfd-2.21.1.so library.

Instead of going into my cross-compile tool-chain directory ..it is going into my system /usr/lib/ directory which contain simple compiled libbfd.so library..

Since i am newbie in linux... please help me

Thanks,
Amit

theNbomr · 08-07-2012, 05:22 PM

libbfd is not familiar to me. Is it created along with your cross toolchain? If not, I don't think the compiler will look for it in it's sysroot directory tree (and it does sound like your toolchain was built with a sysroot). You can try setting environment variables like CC, CFLAGS, LDFLAGS, etc to specify where the compiler & linker should look for headers, libraries, etc. These can also be specified on the commandline, or you can edit the Makefile to do this.

Examples:

Code:

LDFLAGS='-L /some/special/library/location' make
##  or...
make LDFLAGS+='-L /some/special/library/location'

--- rod.