summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/libtool
AgeCommit message (Collapse)AuthorFiles
2013-05-12libtool-nativesdk: rename to nativesdk-libtoolWenzong Fan1
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} Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-02-13libtool-native_2.4.2.bb: Always use /bin/sed for SEDJason Wessel1
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. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-20libtool-cross: Add missing libltdl components to installRichard Purdie1
Without this some software fails to build complaining it can't find these utilities. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-07libtool: remove help2man dependencyMarko Lindqvist3
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 Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-17libtool: Ensure the paths to sed are not hardcodedRichard Purdie1
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-24libtool: update rpath normalization to use builtinAndy Ross2
Use the built-in normalization function instead of the sed hack. Signed-off-by: Andy Ross <andy.ross@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-22libtool: normalize link paths before considering for RPATHAndy Ross2
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. Signed-off-by: Andy Ross <andy.ross@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-19libtool: add ${PN} in middle of package list to ensure .m4 get with ${PN}Saul Wold1
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. Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-06-11libtool: Let -fstack-protector passed to link stepKhem Raj2
linker should add -lssp to linker cmdline when -fstack-protector therefore add this knowledge to libtool otherwise packages will fail to link Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-24libtool: fixed parallel build related raceEnrico Scholz1
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 Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
2012-01-27libtool 2.4.2: fix missing quote in FILES_libtldtlKoen Kooi1
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. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-24libtool: refactor packages for staticdevSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-01-24Fix Upstream-Status entriesSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-01-17libtool: Put all libltdl headers in the correct libltdl-dev packageColin Walters1
/usr/include/ltdl.h was in libtldl-dev, but not the headers it depends on.
2011-12-15libtool-cross: Add libtool & libtoolize to SSTATE_SCAN_FILESSaul Wold1
This fixes problems where hardcoded paths in the file were incorrect during sstate reusage of the task output. Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-12-01libtool: Upgrade from 2.4 -> 2.4.2Nitin A Kamble15
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 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>
2011-11-24libtool: Avoid relinking when cross compiling, its pointlessRichard Purdie3
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-21libtool-cross: Unbreak and actually use more of itRichard Purdie1
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-10Allow use of dash as /bin/shRichard Purdie1
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 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]
2011-09-26libtool: Fix an issue where unnecessary rpaths were being injectedRichard Purdie6
libtool was being to aggressive in adding rpath to binaries. This change stops it adding them if that path the default search path. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-18gcc: remove unused patches and move patches in proper dirNitin A Kamble3
gcc: update upstream-status for patches python: update upstream-status for patches libtool: update upstream-status of patches m4: update upstream status for patches eglibc: remove unused patches eglibc: update upstream status of patches glibc: update upstream-status of patches & remove unused patches Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-05-13recipes: Update upstream-status of patchesNitin A Kamble8
python: update upstream-status for patches binutils: update upstream-status for patches gcc 4.5.1 4.6.0: update upstream-status for patches autoconf: update upstream-status for patches automake: update upstream-status for patches bison: update upstream-status for patches distcc: update upstream-status of patches fstests: update upstream-status for patches gdb: update upstream-status of patches intltool: update upstream-status of patches libtool: update upstream status of patches linux-libc-headers: update upstream-status for patches make: update upstream-status for patches perl: update upstream-status for patches python-pycurl: update upstream-status for patches python-pygobject: update upstream status for patches python-pyrex: update upstream-status for patches quilt: update upstream-status of patches tcl: update upstream-status for patches gnu-config: update upstream-status for patches gmp: update upstream-status for patches Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-03-01Fix to the libtool LICENSE field: libtool.incBeth Flanagan1
License parser should use & not , Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
2011-02-21libtool: avoid absolute pathnames of general utilsNitin A Kamble6
addded a new patch: libtool/avoid_absolute_paths_for_general_utils.patch This fixes [BUGID #154] This fixes [BUGID #734] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-01-21staging: Use relative path in sysroot-destdir for target recipesDongxiao Xu3
Original we used absolute path in sysroot-destdir for both native and target recipes. This commit changes target recipes to use relative path which is same as the image directory. [sgw: merged with libtool sysroot work] Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-21libtool: fix library RPATHsScott Garman2
Enabling sysroot support exposed a bug where the final library had an RPATH encoded into it which still pointed to the sysroot. This works around the issue until it gets sorted out upstream. Fix suggested by Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21libtool: Changes to enable sysroot supportScott Garman9
* Added OE patches by Khem Raj which enable sysroot support and rename the command line option --with-sysroot to --with-libtool-sysroot to avoid conflicts with binutils and gcc * Removed obsolete cross_compile.patch * Changed SRC_URI_append to SRC_URI += * PR bump for all recipes Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21libtool: Move common version specific data to a common include fileRichard Purdie5
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21libtool: Small cleanups of metadataScott Garman3
[based on sections of a patch by Scott Garman extracted by Richard] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-20libtool: Adjusted content of various libtool packages.Lianhao Lu3
[BUGID #562] fixing: 1. Adjusted the content of various packages generated by libtool. 2. Added libtool-nativesdk into task-sdk-host. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2010-12-16recipes-devtools: Add Summary informationMark Hatle1
Add Summary information and update Descripts as necessary. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2010-12-09SRC_URI Checksums AdditionalsSaul Wold2
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-11-18libtool upgrade from 2.2.10 to 2.4Nitin A Kamble6
Taking out of this code from patch as the newer upstream code has fix, and this patch is not needed. cross-compile.patch: -Index: libtool-2.2.10/libltdl/config/ltmain.m4sh +Index: libtool-2.4/libltdl/config/ltmain.m4sh =================================================================== ---- libtool-2.2.10.orig/libltdl/config/ltmain.m4sh -+++ libtool-2.2.10/libltdl/config/ltmain.m4sh -@@ -5147,8 +5147,14 @@ func_mode_link () - absdir="$abs_ladir" - libdir="$abs_ladir" - else -- dir="$libdir" -- absdir="$libdir" -+ # Adding 'libdir' from the .la file to our library search paths -+ # breaks crosscompilation horribly. We cheat here and don't add -+ # it, instead adding the path where we found the .la. -CL -+ dir="$abs_ladir" -+ absdir="$abs_ladir" -+ libdir="$abs_ladir" -+ #dir="$libdir" -+ #absdir="$libdir" - fi - test "X$hardcode_automatic" = Xyes && avoidtemprpath=yes - else Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2010-08-27Major layout change to the packages directoryRichard Purdie9
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-03 06:58:19 +0000