Hi Martin, Le Fri, 3 Feb 2012 10:41:05 +0100, Martin Jansa <martin.ja...@gmail.com> a écrit : > in x86_64-oesdk-linux there are only gcc+binutils crosssdk > binutils-crosssdk-2.22-r2 gcc-crosssdk-4.6.2+svnr181430-r22 > gcc-crosssdk-initial-4.6.2+svnr181430-r22 > gcc-crosssdk-intermediate-4.6.2+svnr181430-r22 > the rest is in > x86_64-nativesdk-oesdk-linux > > gdb-cross-canadian-arm is only package were exec_prefix points to > oecore-x86_64-arm > ./gdb-cross-canadian-arm-7.3.1-r5.1/temp/run.do_configure.1688 > export > exec_prefix="/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr" > > while all nativesdk packages are using oecore-x86_64-x86_64 > ./python-nativesdk-2.7.2-r0.5/temp/run.do_configure.14043 > export > exec_prefix="/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr" > here is the big difference when using Angstrom : python-nativesdk-2.7.2-r0.5/temp/run.do_configure.30951:73:export exec_prefix="/usr/local/angstrom-eglibc-x86_64-armv7a/sysroots/x86_64-angstromsdk-linux/usr" I don't yet know where this difference comes from.
Eric -- http://eukrea.com/en/news/104-2012 _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
