Hi again,
On 06/10/10 09:06, Jose V Beneyto wrote:
Hey Victor,
On 06/08/10 10:44, [email protected] wrote:
[...]
There is another thing that seems to don't hurt (may be there is a
lack of knowledge
from my side atm), for example:
[piti...@safe-env /des/crux-arm/toolchain/clfs/usr/lib]$ objdump -x
libstdc++.so|grep RPATH
RPATH
/des/crux-arm/toolchain/crosstools/arm-crux-linux-gnueabi/lib
This means that libtool will try on native builds to locate this
path, but it doesn't
exists and it will not be used.
[...]
some tests I made:
$ export PATH=$PATH:/devel/crux-arm/toolchain/crosstools/bin
$ unset CFLAGS; unset CXXFLAGS; unset CC
$ cat > test.c
#include <stdio.h>
int main(int argc, char ** argv) {
printf("CRUX ARM Test\n");
return 0;
}
$ arm-crux-linux-gnu-gcc -Wall -o test test.c
$ arm-crux-linux-gnu-objdump -x test | grep -i rpath
$ arm-crux-linux-gnu-gcc -Wall -Wl,-rpath,/usr/lib -o test2 test.c
$ arm-crux-linux-gnu-objdump -x test2 | grep -i rpath
RPATH /usr/lib
$ arm-crux-linux-gnu-gcc -Wall -Wl,-rpath,/devel/crux-arm/crosstools/lib
-o test3 test.c
$ arm-crux-linux-gnu-objdump -x test3 | grep -i rpath
RPATH /devel/crux-arm/crosstools/lib
seems that in cross-generated packages just we need to look for and
cleanup flags containing rpath,
so there are some with LDFLAGS="-Wl,-rpath,$(CROSSTOOLS)/lib":
$ find ports/ -type f -name Pkgfile -exec grep -H -i rpath {} \; | cut
-d':' -f1
ports/opt-cross/irssi/Pkgfile
ports/opt-cross/navit/Pkgfile
ports/opt-cross/libmpeg2/Pkgfile
ports/games-cross/opentyrian/Pkgfile
ports/games-cross/prboom/Pkgfile
ports/games-cross/xmoto/Pkgfile
ports/core-cross-noeabi/gcc/Pkgfile <--------- most important
for what I know we should keep rpath only for the toolchain and not for
production packages
Regards,
--
Jose V Beneyto | http://mikeux.dyndns.org
_______________________________________________
crux-arm mailing list
[email protected]
http://crux-arm.nu/mailman/listinfo/crux-arm
