linux/poky.git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb, branch mickledore-next

libtool: upgraded to 2.4.4

2015-01-23T11:36:26+00:00

* Upgrade: - libtool-native - libtool-cross - nativesdk-libtool - libtool * Remove 2 patches: - respect-fstack-protector.patch: already in the new source. - avoid_absolute_paths_for_general_utils.patch: no general.m4sh any more. - Use inline-source to install libtoolize. * Update other patches * The LIC_FILES_CHKSUM is changed because of the indent, the contents are the same. * The libtool config files are put in libtool/build-aux now, it was libtool/config in the past. (From OE-Core rev: 871dc461b1dfc431c0c95743af1624b781262bce) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

libtool: add bash to RDEPENDS_libtool

2014-08-23T08:26:10+00:00

* Set CONFIG_SHELL="/bin/bash" * Add bash to RDEPENDS_libtool We had already set CONFIG_SHELL="/bin/bash" for libtool-native, libtool-cross and nativesdk-libtool, now also set for target libtool, if we don't set this, libtool would use /bin/sh, /bin/bash, /bin/ksh or /bin/sh5 according to the host, and the build is undetermined, this patch can fix the problem, libtool is a development tool, rdepends on bash should not cause toubles (for example, the size of the image) Have tried to set CONFIG_SHELL="/bin/sh" (/bin/sh -> dash), but there is still a few bashsim in the output libtool. (From OE-Core rev: c07f09b1b261b0d480544a6100f6a83835c62019) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

libtool-cross/native: Force usage of bash due to sstate inconsistencies

2014-01-23T12:18:05+00:00

Scenario: a) libtool script is built on system with bash as /bin/sh b) machine B installs sstate from build a) c) machine B has dash as /bin/sh In this scenario, the script fails to work properly since its expecting /bin/sh to have bash like syntax and it no longer does have it. This patch forces the configure process to use /bin/bash, not /bin/sh and hence allows the scripts to work correctly when used from sstate. (From OE-Core rev: 24d5b449e5f4d91119f0d8e13c457618811aadfc) Signed-off-by: Richard Purdie

gcc/libtool/perl: Fix various path to sed-native problems

2013-09-26T15:37:56+00:00

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

libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-02-13T16:52:30+00:00

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.2

2011-12-01T20:40:23+00:00

Rebased patches to the newer source code and deleted resolve-sysroot.patch since its already applied upstream merged libtool-2.4.2.inc & libtool.inc 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