summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/libtool
Commit message (Collapse)AuthorAgeFilesLines
* libtool: remove /absolute/path/to/host referencesOoi Cinly2017-08-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | Removed all instances of -fdebug-prefix-map in LTCFLAGS declaration because they contain references to host system and are not needed. /absolute/path/to/host/dd was replaced with 'dd' in lt_truncate_bin declaration. Please take note that the location of regex is important for DEBUG_PREFIX_MAP. Removal of DEBUG_PREFIX_MAP has to be done before other regex command modify its option value. Both are modified because they affect binary reproducibility. [YOCTO #11656] (From OE-Core rev: 04db02138e363898e040e33557f1296e8a43c3fd) Signed-off-by: Ooi Cinly <cinly.ooi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Add/fix missing Upstream-Status to patchesRichard Purdie2017-06-271-0/+2
| | | | | | | | | This adds or fixes the Upstream-Status for all remaining patches missing it in OE-Core. (From OE-Core rev: 563cab8e823c3fde8ae4785ceaf4d68a5d3e25df) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Switch to Recipe Specific SysrootsRichard Purdie2017-01-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is comparatively large and invasive. It does only do one thing, switching the system to build using recipe specific sysroots and where changes could be isolated from it, that has been done. With the current single sysroot approach, its possible for software to find things which aren't in their dependencies. This leads to a determinism problem and is a growing issue in several of the market segments where OE makes sense. The way to solve this problem for OE is to have seperate sysroots for each recipe and these will only contain the dependencies for that recipe. Its worth noting that this is not task specific sysroots and that OE's dependencies do vary enormously by task. This did result in some implementation challenges. There is nothing stopping the implementation of task specific sysroots at some later point based on this work but that as deemed a bridge too far right now. Implementation details: * Rather than installing the sysroot artefacts into a combined sysroots, they are now placed in TMPDIR/sysroot-components/PACKAGE_ARCH/PN. * WORKDIR/recipe-sysroot and WORKDIR/recipe-sysroot-native are built by hardlinking in files from the sysroot-component trees. These new directories are known as RECIPE_SYSROOT and RECIPE_SYSROOT_NATIVE. * This construction is primarily done by a new do_prepare_recipe_sysroot task which runs before do_configure and consists of a call to the extend_recipe_sysroot function. * Other tasks need things in the sysroot before/after this, e.g. do_patch needs quilt-native and do_package_write_deb needs dpkg-native. The code therefore inspects the dependencies for each task and adds extend_recipe_sysroot as a prefunc if it has populate_sysroot dependencies. * We have to do a search/replace 'fixme' operation on the files installed into the sysroot to change hardcoded paths into the correct ones. We create a fixmepath file in the component directory which lists the files which need this operation. * Some files have "postinstall" commands which need to run against them, e.g. gdk-pixbuf each time a new loader is added. These are handled by adding files in bindir with the name prefixed by "postinst-" and are run in each sysroot as its created if they're present. This did mean most sstate postinstalls have to be rewritten but there shouldn't be many of them. * Since a recipe can have multiple tasks and these tasks can run against each other at the same time we have to have a lock when we perform write operations against the sysroot. We also have to maintain manifests of what we install against a task checksum of the dependency. If the checksum changes, we remove its files and then add the new ones. * The autotools logic for filtering the view of m4 files is no longer needed (and was the model for the way extend_recipe_sysroot works). * For autotools, we used to build a combined m4 macros directory which had both the native and target m4 files. We can no longer do this so we use the target sysroot as the default and add the native sysroot as an extra backup include path. If we don't do this, we'd have to build target pkg-config before we could built anything using pkg-config for example (ditto gettext). Such dependencies would be painful so we haven't required that. * PKDDATA_DIR was moved out the sysroot and works as before using sstate to build a hybrid copy for each machine. The paths therefore changed, the behaviour did not. * The ccache class had to be reworked to function with rss. * The TCBOOTSTRAP sysroot for compiler bootstrap is no longer needed but the -initial data does have to be filtered out from the main recipe sysroots. Putting "-initial" in a normal recipe name therefore remains a bad idea. * The logic in insane needed tweaks to deal with the new path layout, as did the debug source file extraction code in package.bbclass. * The logic in sstate.bbclass had to be rewritten since it previously only performed search and replace on extracted sstate and we now need this to happen even if the compiled path was "correct". This in theory could cause a mild performance issue but since the sysroot data was the main data that needed this and we'd have to do it there regardless with rss, I've opted just to change the way the class for everything. The built output used to build the sstate output is now retained and installed rather than deleted. * The search and replace logic used in sstate objects also seemed weak/incorrect and didn't hold up against testing. This has been rewritten too. There are some assumptions made about paths, we save the 'proper' search and replace operations to fixmepath.cmd but then ignore this. What is here works but is a little hardcoded and an area for future improvement. * In order to work with eSDK we need a way to build something that looks like the old style sysroot. "bitbake build-sysroots" will construct such a sysroot based on everything in the components directory that matches the current MACHINE. It will allow transition of external tools and can built target or native variants or both. It also supports a clean task. I'd suggest not relying on this for anything other than transitional purposes though. To see XXX in that sysroot, you'd have to have built that in a previous bitbake invocation. * pseudo is run out of its components directory. This is fine as its statically linked. * The hacks for wayland to see allarch dependencies in the multilib case are no longer needed and can be dropped. * wic needed more extensive changes to work with rss and the fixes are in a separate commit series * Various oe-selftest tweaks were needed since tests did assume the location to binaries and the combined sysroot in several cases. * Most missing dependencies this work found have been sent out as separate patches as they were found but a few tweaks are still included here. * A late addition is that extend_recipe_sysroot became multilib aware and able to populate multilib sysroots. I had hoped not to have to add that complexity but the meta-environment recipe forced my hand. That implementation can probably be neater but this is on the list of things to cleanup later at this point. In summary, the impact people will likely see after this change: * Recipes may fail with missing dependencies, particularly native tools like gettext-native, glib-2.0-native and libxml2.0-native. Some hosts have these installed and will mask these errors * Any recipe/class using SSTATEPOSTINSTFUNCS will need that code rewriting into a postinst * There was a separate patch series dealing with roots postinst native dependency issues. Any postinst which expects native tools at rootfs time will need to mark that dependency with PACKAGE_WRITE_DEPS. There could well be other issues. This has been tested repeatedly against our autobuilders and oe-selftest and issues found have been fixed. We believe at least OE-Core is in good shape but that doesn't mean we've found all the issues. Also, the logging is a bit chatty at the moment. It does help if something goes wrong and goes to the task logfiles, not the console so I've intentionally left this like that for now. We can turn it down easily enough in due course. (From OE-Core rev: 809746f56df4b91af014bf6a3f28997d6698ac78) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysrootPeter Kjellerstedt2016-05-131-8/+5
| | | | | | (From OE-Core rev: 83cdfd77b1b48f2bd648d3a5991eadb7f01f647e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Use SYSROOT_DIRS to add dirs to stage in sysrootPeter Kjellerstedt2016-05-131-6/+1
| | | | | | (From OE-Core rev: 8f0c872a496fe70ac02cd745aef36d2f36cf0d49) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: fix contaminated path to lt_truncate_binAlexandru Moise2016-04-061-0/+1
| | | | | | | | | | | | | | | | | | lt_truncate_bin path is contaminated by the path from the sysroot directory for the build host. Steps to reproduce this issue: $ bitbake -c cleanall libtool $ bitbake coreutils-native $ bitbake libtool $ grep -in "lt_truncate_bin=" tmp/work/*/libtool/*/image/usr/bin/libtool (From OE-Core rev: 5e83a72f1ec834063d27b924bc7f9a047204cec6) Signed-off-by: Alexandru Moise <alexandru.moise@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Don't hardcode grep pathsRichard Purdie2016-02-191-0/+2
| | | | | | | | | If sharing sstate between different distros, some of which have /bin/grep and some /usr/bin/grep, this can break. Simply don't hardcode the path. (From OE-Core rev: f6e7a3b1ac75c274493666b9a31cca83b7d2138b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Unset pre|post dep objectsKhem Raj2016-02-021-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | predep_objects and postdep_objects are specifying the duplicate objects which are better computed by gcc/g++ driver, since we want to generate PIE, PIC and non-PIC combinations, let gcc decide on this, since it knows best about linker options to use in each of these situations. When we defer the linker options to driver, we also need to remove -nostdlib from linker commandline options. Remove duplicate directory creation for ${D}${bindir_crossscripts}/ This fixes a frequent problem we see during -fpie links e.g. | /home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/qemux86-64/usr/include/c++/5.3.0/iostream:74: undefined reference to `__dso_handle' | /home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/x86_64-linux/usr/libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/5.3.0/ld: .libs/cxx_channel.o: relocation R_X86_64_PC32 against undefined hidden symbol `__dso_handle' can not be used when making a shared object | /home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/x86_64-linux/usr/libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/5.3.0/ld: final link failed: Bad value After this change libtool gets changed as below old_archive_from_expsyms_cmds="" # Commands used to build a shared archive. -archive_cmds="\$CC \$pic_flag -shared -nostdlib \$predep_objects \$libobjs \$deplibs \$postdep_objects \$compiler_flags \$wl-soname \$wl\$soname -o \$lib" -archive_expsym_cmds="\$CC \$pic_flag -shared -nostdlib \$predep_objects \$libobjs \$deplibs \$postdep_objects \$compiler_flags \$wl-soname \$wl\$soname \$wl-retain-symbols-file \$wl\$export_symbols -o \$lib" +archive_cmds="\$CC \$pic_flag -shared \$predep_objects \$libobjs \$deplibs \$postdep_objects \$compiler_flags \$wl-soname \$wl\$soname -o \$lib" +archive_expsym_cmds="\$CC \$pic_flag -shared \$predep_objects \$libobjs \$deplibs \$postdep_objects \$compiler_flags \$wl-soname \$wl\$soname \$wl-retain-symbols-file \$wl\$export_symbols -o \$lib" # Commands used to build a loadable module if different from building # a shared archive. @@ -11908,8 +11908,8 @@ # Dependencies to place before and after the objects being linked to # create a shared library. -predep_objects="/home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/qemux86-64/usr/lib/../lib/Scrt1.o /home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/qemux86-64/usr/lib/../lib/crti.o /home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/qemux86-64/usr/lib/../lib/x86_64-oe-linux/5.3.0/crtbeginS.o" -postdep_objects="/home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/qemux86-64/usr/lib/../lib/x86_64-oe-linux/5.3.0/crtendS.o /home/ubuntu/work/oe/openembedded-core/build/tmp-glibc/sysroots/qemux86-64/usr/lib/../lib/crtn.o" +predep_objects="" +postdep_objects="" predeps="" postdeps="-lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc" (From OE-Core rev: e1b45cb8e15458dde21f5e86ea1cbb619fb5c4cf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Fix nios2 supportMarek Vasut2015-09-232-0/+69
| | | | | | | | | | Add patch to fix excessive greediness of OS/2 check in libtool. (From OE-Core rev: 1bd71e740b085d2e012b38ac5c04556d7f8561c4) Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Fix regression from previous commitRichard Purdie2015-07-091-1/+1
| | | | | | | | | | | | | | Commit http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=f44aa10ec122df309d9810d4d25fbb8f799107d2 inadvertently moved the m4 macros to the -dev package. These need to be in the main package since libtoolize is useless without them. Move them back (as the commented code implies was always needed) [YOCTO #7889] (From OE-Core rev: 5a1f80e15d7fb60fd7c2b82aa769adef95d877a9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: remove libltdl-dev libltdl-dbg libltdl-staticdev from PACKAGESRobert Yang2015-04-131-8/+1
| | | | | | | | | There should be only one dev and dbg package (From OE-Core rev: 5e40bcd93d9ea64f1a6d75e62aabda3dcb33fc01) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: put libltdl.la in the right package.Li Zhou2015-03-101-0/+1
| | | | | | | | | | | | The libltdl libraries are put in libltdl-* packages, but libltdl.la is packaged in libtool-dev. This change puts libltdl.la in libltdl-dev package instead of libtool-dev. (From OE-Core rev: bcf1f0e18c656f75d8d1b8bbe1607bd8c722b529) Signed-off-by: Li Zhou <li.zhou@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: 2.4.5 -> 2.4.6Richard Purdie2015-02-176-74/+2
| | | | | | | | Drop patch merged upstream. (From OE-Core rev: cd03ef79b50ed42b9d407ee45fc3e3321385281c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: don't execute automake and autoconf on every invocationRobert Yang2015-02-152-0/+72
| | | | | | | | | | | | | | | From the origin commit message: Regression from 2.4.2 was causing noticable slow-down in builds that call libtool many times. * build-aux/ltmain.in (func_help): Override func_help() from gl/build-aux/options-parser to only run automake --version and autoconf --version when libtool --help is executed on the command line. (From OE-Core rev: 9fd23c9ac03143b578559bb79995f2655c81ccc8) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "libtool: avoid running automake/autoconf --version"Robert Yang2015-02-152-55/+0
| | | | | | | | | | | This reverts commit 1f53edeaf9ea59dd55459a6d5a93829fb4983839. There is a better fix on upstream, will backport it. (From OE-Core rev: 600c9bb271a47674876b029a6a58ffac08add8ed) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Fix option parsing performance regressionRichard Purdie2015-02-102-0/+180
| | | | | | | | | | | Cut and paste the pieces of build-aux/options-parser inline into the main ltmain.sh code. This removes a performance degradation caused by the repeated calls to func_quote_for_eval, the mechanism funclib uses to construct the functions used for option parsing. (From OE-Core rev: 6bf5cbbcac80ee818cc932d69227e70e41ce02d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: avoid running automake/autoconf --versionRobert Yang2015-02-052-0/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The libtool would be very slow if run "automake/autoconf --version", for example, when compile xz-native (make -j1, only compile, no confiure or install): before patched: 19s after patched: 11s Use plain text to instead of running them. NOTE: it is still a little slower than libtool 2.4.2 when compile xz-native because of other parts: make -j1: about 2s slower make -j32: about 0.4s slower If we run to do_install: (PARALLEL_MAKE = "-j32") libtool 2.4.2: $ bitbake xz-native -cinstall && bitbake xz-native -ccleansstate && time bitbake xz-native -cinstall real 0m21.092s user 0m28.292s sys 0m3.932s libtool 2.4.5: $ bitbake xz-native -cinstall && bitbake xz-native -ccleansstate && time bitbake xz-native -cinstall real 0m21.380s user 0m31.140s sys 0m4.068s About 0.3s, slightly different. But when using /bin/bash as CONFIG_SHELL, the new libtool would be much slower: real 0m23.106s user 0m44.044s sys 0m4.280s About 2s slower, for the big package like cairo, it is more slower (about 6s), unfortunately, /bin/bash is most default CONFIG_SHELL for the recipes since configure checks first check bash. (From OE-Core rev: eb9d896db2fc67bac8efd258744d06fbbee87f06) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Fix tools path issuesRichard Purdie2015-02-032-0/+28
| | | | | | | | | | | | | | | | If for example you build on a machine with /bin/grep, then restore that sstate onto a machine with /usr/bin/grep, things will fail. Simply don't bother hardcoding paths. This was lost during the libtool upgrade: http://git.yoctoproject.org/cgit.cgi/poky/diff/meta/recipes-devtools/libtool/libtool/avoid_absolute_paths_for_general_utils.patch?id=d4e1862453b2a4c12400de0f43f08a9871a4de60 since the path to the files changed. This restores the previous behaviour. (From OE-Core rev: e48c06264f183c3d611a20a45914e9eeaa8f3736) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: 2.4.4 -> 2.4.5Richard Purdie2015-02-025-2/+2
| | | | | | (From OE-Core rev: 8156469a2ff36521aefcc9a3a4125d2dbcd4711a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: upgraded to 2.4.4Robert Yang2015-01-2317-285/+184
| | | | | | | | | | | | | | | | | | | | | | | | | | | * 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 <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: remove build host paths from installed libtoolShiqun Lin2014-11-121-0/+11
| | | | | | | | | | | | | | | | | | | | | Resulted libtool contains references about paths from the build host Below variables contains hard coded build paths from the host: LTCC= lt_sysroot= sys_lib_search_path_spec= LD= CC= compiler_lib_search_dirs= predep_objects= postdep_objects= compiler_lib_search_path= (From OE-Core rev: d27c4226f600584f83f66c86b0988a165e8ecb75) Signed-off-by: Shiqun Lin <Shiqun.Lin@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Extend fix-final-rpath.patchRandy Witt2014-10-241-2/+14
| | | | | | | | | | | | | | | When building upower from meta-oe, the following QA error occurred: ERROR: QA Issue: package upower contains bad RPATH It appears to have been caused by one of the cases fix-final-rpath.patch is meant to address but missed. So this change fixes the additional case that was causing upower to have the QA error. (From OE-Core rev: d2b2bb7cedb678c9f67ef1d9170fc427d9beee1e) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: add bash to RDEPENDS_libtoolRobert Yang2014-08-235-6/+4
| | | | | | | | | | | | | | | | | | | | * 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 <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add texinfo.bbclass; recipes that use texinfo utils at build-time inherit it.Max Eliaser2014-05-021-1/+1
| | | | | | | | | | | | | 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 <max.eliaser@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Set CONFIG_SHELL for nativesdkRichard Purdie2014-01-311-0/+2
| | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* libtool-cross/native: Force usage of bash due to sstate inconsistencies1.6_M2Richard Purdie2014-01-232-0/+3
| | | | | | | | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* libtool: remove the unrecognized configure optionChen Qi2014-01-231-2/+0
| | | | | | | | | | Remove the unrecognized configure option '--with-sysroot' to avoid build time warnings. (From OE-Core rev: 6f6a10372b6a318be7695b6b50275a8a3e9ed033) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Don't patch generated filesRichard Purdie2013-09-301-660/+0
| | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc/libtool/perl: Fix various path to sed-native problemsRichard Purdie2013-09-262-4/+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 <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: fix resolve of lt_sysrootHans Beckerus2013-09-172-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | 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 <hans.beckerus at gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-nativesdk: rename to nativesdk-libtoolWenzong Fan2013-05-121-0/+6
| | | | | | | | | | | | | | 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 <wenzong.fan@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-native_2.4.2.bb: 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 <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Add missing libltdl components to installRichard Purdie2013-01-201-0/+3
| | | | | | | | | Without this some software fails to build complaining it can't find these utilities. (From OE-Core rev: db84eaf851b22b262d9dc48eb55bd5224a00fdd2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: remove help2man dependencyMarko Lindqvist2013-01-073-23/+26
| | | | | | | | | | | | | | Remove manpage creation. It wasn't working because of help2man missing when libtool is being built. This attempt to create manpages without help2man turns from no-op to hard error with automake-1.13. Removed prefix-manpage-fix.patch as only code it touched is being removed by new dont-depend-on-help2man.patch (From OE-Core rev: 51a97cfb96ee2e5eeef978678fe6acdd498b9555) Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Ensure the paths to sed are not hardcodedRichard Purdie2012-10-181-0/+3
| | | | | | | | | | | | | | | | | If you: bitbake sed-native bitbake libtool-cross then libtool-cross has SED="/path/to/sysroot/sed" which is incorrect. If that is reused from sstate or sed-native is cleaned, the build will fail. This patch simply sets sed to be "sed" since we're not on systems where the sed from PATH is broken. (From OE-Core rev: 86c6fa8175482283268dfa8782c6643a3510e0fd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: update rpath normalization to use builtinAndy Ross2012-08-242-15/+9
| | | | | | | | | Use the built-in normalization function instead of the sed hack. (From OE-Core rev: ba8263e5dc520f5024fc76d8bd2e10fe0564b0e2) Signed-off-by: Andy Ross <andy.ross@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: normalize link paths before considering for RPATHAndy Ross2012-08-222-0/+43
| | | | | | | | | | | Libtool may be passed link paths of the form "/usr/lib/../lib", which fool its detection code into thinking it should be included as an RPATH in the generated binary. Normalize before comparision. (From OE-Core rev: e3b0925f4c861393e436deb6b1912f9f1f325d1e) Signed-off-by: Andy Ross <andy.ross@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: add ${PN} in middle of package list to ensure .m4 get with ${PN}Saul Wold2012-06-211-1/+6
| | | | | | | | | | | With the new order scheme, ${PN} needs to be in the middle for the .m4 files to be packaged, otherwise the move the -dev package which is wrong in this case. (From OE-Core rev: 57ad9075ea7521e8fa20d62aac31afb2e2130348) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Let -fstack-protector passed to link stepKhem Raj2012-06-112-1/+55
| | | | | | | | | | | linker should add -lssp to linker cmdline when -fstack-protector therefore add this knowledge to libtool otherwise packages will fail to link (From OE-Core rev: d1756ff379ab310bfa6323d8643b7e9d764f94bf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: fixed parallel build related raceEnrico Scholz2012-05-241-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | While building libtool, the libtool script itself will be regenerated because OE modifies a dependency[1]. With -jX, this operation (--> removal, creation of non-x file, 'chmod a+x') can happen at a time when the script is going to be executed. This can cause errors like: | arm-linux-gnueabi-libtool: compile: ccache arm-linux-gnueabi-gcc ... | ... | /bin/sh ./config.status libtool | ... | arm-linux-gnueabi-libtool: compile: ccache arm-linux-gnueabi-gcc ... | /bin/sh: ./arm-linux-gnueabi-libtool: Permission denied | make[2]: *** [libltdl/libltdl_libltdl_la-lt__alloc.lo] Error 126 I am not sure whether the custom do_compile_prepend() is still needed. For now only the issue above will be fixed by executing ./config.status yet again. [1] see 648290d5bf4d6ff50d3643bb7ad902dfc23aa702 (From OE-Core rev: e065c11b6066f8c1d37496b58dd853a684cd9136) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool 2.4.2: fix missing quote in FILES_libtldtlKoen Kooi2012-01-271-2/+2
| | | | | | | | | | | | | | The missing quote prohibits OE from packaging it correctly, leading to: | * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-gnome: | * libltdl7 (>= 2.4.2) * libltdl7 (>= 2.4.2) * libltdl7 (>= 2.4.2) * libltdl7 (>= 2.4.2) * libltdl7 (>= 2.4.2) * libltdl7 (>= 2.4.2) * libltdl7 (>= 2.4.2) * for incremental builds and binary feeds. (From OE-Core rev: ed6968b731e8ebc161fa59e18a9284bddf86c61b) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: refactor packages for staticdevSaul Wold2012-01-241-4/+5
| | | | | | | (From OE-Core rev: 63bfddf162cea836748e56da1488de56758d0418) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fix Upstream-Status entriesSaul Wold2012-01-241-1/+1
| | | | | | | (From OE-Core rev: 0cd9314ef95168ba5452a01ed8d923585c8d54ae) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Put all libltdl headers in the correct libltdl-dev packageColin Walters2012-01-171-1/+1
| | | | | | | /usr/include/ltdl.h was in libtldl-dev, but not the headers it depends on. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Add libtool & libtoolize to SSTATE_SCAN_FILESSaul Wold2011-12-151-1/+3
| | | | | | | | | | This fixes problems where hardcoded paths in the file were incorrect during sstate reusage of the task output. (From OE-Core rev: 69dfde005c7018b99a0397f4233841d76e383b4c) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Upgrade from 2.4 -> 2.4.2Nitin A Kamble2011-12-0115-208/+168
| | | | | | | | | | | | | | | 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 <nitin.a.kamble@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Avoid relinking when cross compiling, its pointlessRichard Purdie2011-11-243-2/+105
| | | | | | | | | | | | | | | | | | | | There is no point in having "executable" binaries in the .libs directory linked with different rpaths to the target which could concivably be run on the build system when cross compiling. This patch removes the extra rpaths ($compile_rpath) so that the output from the "link" stage can be used on the target. We can then avoid having to "relink" during the install stage. This saves some build time (do_install is over 2 minutes faster for pulseaudio). This patch also removes an annoying "seems to be moved" warning which is totally bogus in the sysroot case. (From OE-Core rev: 0a1dedeb8eea4e230b47d1516b3e6e90495fe49d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Unbreak and actually use more of itRichard Purdie2011-11-211-11/+15
| | | | | | | | | | | | | | We should be using libtool-cross for cross compiling but were not. This patch sets datadir so libtoolize ends up containing correct paths. It then installs libtoolize. The path ltmain.sh was installed to was incorrect and this is fixed. We also now install all the libtool m4 macros and config files. (From OE-Core rev: d52bdbee35bb6edc55eed613f869e46d0c0a2f31) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Allow use of dash as /bin/shRichard Purdie2011-11-101-1/+10
| | | | | | | | | | | | | | | | | | | | | | | We've had the check for dash as /bin/sh for a long time. Dash has been around long enough now that most major issues have been identified and fixed from build perspective. This patch fixes a bashism in the openjade-native recipe. It also adjusts libtool so that the header at the script is used and not the value of $SHELL. This is because many Makefiles change $SHELL so dash can get used to execute what is otherwise configured as a bash shell script. Since we don't need to execute scripts this way on any system I'm aware of us building upon, the simplest fix is just to remove $SHELL. With these two changes the dash check can be removed and we can allow builds with dash as /bin/sh (From OE-Core rev: 07ded02ffd37b4fe60a6210dbf56490ea306f0b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> [Note: I know I need to add the description of the libtool change above into the prefix.patch]
* libtool: Fix an issue where unnecessary rpaths were being injectedRichard Purdie2011-09-266-5/+69
| | | | | | | | | libtool was being to aggressive in adding rpath to binaries. This change stops it adding them if that path the default search path. (From OE-Core rev: 99d1e3ee56c326b3ab68913e68d133a63f334696) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 10:59:41 +0000