path: root/meta/recipes-devtools/libtool/
Commit message (Collapse)AuthorAgeFilesLines
* gcc/libtool/perl: Fix various path to sed-native problemsRichard Purdie2013-09-261-1/+0
| | | | | | | | | | | | | | | | | | | | If sed-native is built before these programs, hardcoded paths to sed-native can end up in scripts and other parts of the system which may cause issues if they are later used from sstate and sed-native is not installed. To avoid this, this patch changes the global site configuration to specify that plain "sed" is fine to be used. We need to spell this out for gcc since it doesn't see the site files since we don't autoreconf it. We can remove the values from libtool. We tell perl to use "/bin/sed" since it requires a path and the system sed should be just fine for it. [YOCTO #4971] (From OE-Core rev: 2ec171cb188601bf18c6c2895870907024b1c52a) Signed-off-by: Richard Purdie <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
* Always use /bin/sed for SEDJason Wessel2013-02-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you never use sstate and always build everything from scratch you will never see this problem. However, if you use sstate and build directories that last a long time eventually you can end up with the scenario where libtool gets a hard coded path in it for sed, and sed may not exist. The reason you don't see this problem to often if you generally build from scratch is that libtool builds before sed and will pickup the host's /bin/sed. The way to reproduce the issue is: bitbake some_image bitbake -c cleansstate libtool-native bitbake sed-native bitbake libtool-native bitbake -c clean sed-native bitbake ANY_PACKAGE_THAT_USES_LIBTOOL_NATIVE In my case I used modphp, which doesn't exist in the oe-core. You will end up with a strange looking error like: | make[1]: *** [buckets/apr_buckets_alloc.lo] Error 1 | /opt/build/bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool: line 981: /opt/build/bitbake_build/tmp/sysroots/x86_64-linux//bin/sed: No such file or directory The solution is to always use /bin/sed for libtool-native. (From OE-Core rev: 605e4484840e70c64acddb4aa1a3c9fec4078d9d) Signed-off-by: Jason Wessel <> Signed-off-by: Richard Purdie <>
* libtool: Upgrade from 2.4 -> 2.4.2Nitin A Kamble2011-12-011-0/+24
Rebased patches to the newer source code and deleted resolve-sysroot.patch since its already applied upstream merged & files replaced PR with ${INC_PR}.0 (From OE-Core rev: aa0cb889a4ef883235dc3f3e1d76ee4a556ae03a) Signed-off-by: Nitin A Kamble <> Signed-off-by: Khem Raj <> Signed-off-by: Richard Purdie <>
OpenPOWER on IntegriCloud