linux/poky.git/meta/recipes-devtools/libtool, branch 1.7_M3

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

Add texinfo.bbclass; recipes that use texinfo utils at build-time inherit it.

2014-05-02T19:46:59+00:00

The class itself currently does nothing. The idea is to mark all recipes that make use of the texinfo utilities. In the future, this class could be used to suppress the generation/formatting of documentation for performance, explicitly track dependencies on these utilities, and eliminate Yocto's current dependency on the host system's texinfo utilities. (From OE-Core rev: e6fb2f9afe2ba6b676c46d1eb297ca9cc532d405) Signed-off-by: Max Eliaser Signed-off-by: Richard Purdie

libtool: Set CONFIG_SHELL for nativesdk

2014-01-31T15:44:21+00:00

We're seeing similar failures that we saw from libtool-native and libtool-cross where /bin/sh changed from bash to dash on different machines after sstate reusage. This patch fixes nativesdk to avoid the same issue. (From OE-Core rev: 7994b2870dac8fd5f6db6d47043378534b644515) 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

libtool: remove the unrecognized configure option

2014-01-23T10:17:32+00:00

Remove the unrecognized configure option '--with-sysroot' to avoid build time warnings. (From OE-Core rev: 6f6a10372b6a318be7695b6b50275a8a3e9ed033) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

libtool: Don't patch generated files

2013-09-30T21:11:57+00:00

We wipe out and regenerate all configure files so there is no point in patching them. (From OE-Core rev: 8d7036cdb71e66e619053c2545cfc1fbddf1895b) Signed-off-by: Richard Purdie Signed-off-by: Saul Wold 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: fix resolve of lt_sysroot

2013-09-17T18:34:56+00:00

This patch updates libtool.m4 (and its output) to resolve a problem with variable 'lt_sysroot' not being properly updated if the option '--with[-libtool]-sysroot' is not provided when running the 'configure' script for a package. According to the help text ouput from 'configure': --with-libtool-sysroot=DIR Search for dependent libraries within DIR (or the compiler's sysrooot if not specified). Due to mixed up cases in a switch statement, when checking if the option was specified or not, wrong actions were taken resulting in an incorrect sysroot and failures to properly locate e.g. .la files when using the populated SDK toolchain. For current upstream status see: http://lists.gnu.org/archive/html/bug-libtool/2013-09/msg00005.html (From OE-Core rev: f5cf7e1a5c85fb320faa9cbeef24f491706b4c1d) Signed-off-by: Hans Beckerus Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

libtool-nativesdk: rename to nativesdk-libtool

2013-05-12T08:37:29+00:00

Rename nativesdk item to prefix vs suffix. Some minor changes for getting it works after renamed: * append patches dir 'libtool/' to FILESEXTRAPATHS * update ${S}, append '${datadir}/libtool/*' to FILES_${PN} (From OE-Core rev: cc7deb8b8dbc58975b8f55cd63f237aa0ded0887) Signed-off-by: Wenzong Fan 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