summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/libtool
AgeCommit message (Collapse)AuthorFiles
2016-05-13libtool: Use SYSROOT_DIRS_BLACKLIST to exclude dirs from the sysrootPeter Kjellerstedt1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-13libtool-cross: Use SYSROOT_DIRS to add dirs to stage in sysrootPeter Kjellerstedt1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-06libtool: fix contaminated path to lt_truncate_binAlexandru Moise1
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 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>
2016-02-18libtool: Don't hardcode grep pathsRichard Purdie1
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-02libtool-cross: Unset pre|post dep objectsKhem Raj1
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" Signed-off-by: Khem Raj <raj.khem@gmail.com>
2015-09-21libtool: Fix nios2 supportMarek Vasut2
Add patch to fix excessive greediness of OS/2 check in libtool. Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-07-09libtool: Fix regression from previous commitRichard Purdie1
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] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-04-13libtool: remove libltdl-dev libltdl-dbg libltdl-staticdev from PACKAGESRobert Yang1
There should be only one dev and dbg package Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-09libtool: put libltdl.la in the right package.Li Zhou1
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. Signed-off-by: Li Zhou <li.zhou@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-02-16libtool: 2.4.5 -> 2.4.6Richard Purdie6
Drop patch merged upstream. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-14libtool: don't execute automake and autoconf on every invocationRobert Yang2
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. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2015-02-14Revert "libtool: avoid running automake/autoconf --version"Robert Yang2
This reverts commit 1f53edeaf9ea59dd55459a6d5a93829fb4983839. There is a better fix on upstream, will backport it. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2015-02-10libtool: Fix option parsing performance regressionRichard Purdie2
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-05libtool: avoid running automake/autoconf --versionRobert Yang2
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. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-03libtool: Fix tools path issuesRichard Purdie2
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-02libtool: 2.4.4 -> 2.4.5Richard Purdie5
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-01-23libtool: upgraded to 2.4.4Robert Yang17
* 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. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2014-11-12libtool: remove build host paths from installed libtoolShiqun Lin1
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= Signed-off-by: Shiqun Lin <Shiqun.Lin@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24libtool: Extend fix-final-rpath.patchRandy Witt1
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. Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-08-23libtool: add bash to RDEPENDS_libtoolRobert Yang5
* 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. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-05-01Add texinfo.bbclass; recipes that use texinfo utils at build-time inherit it.Max Eliaser1
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. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-31libtool: Set CONFIG_SHELL for nativesdkRichard Purdie1
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-23libtool-cross/native: Force usage of bash due to sstate inconsistenciesRichard Purdie2
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-22libtool: remove the unrecognized configure optionChen Qi1
Remove the unrecognized configure option '--with-sysroot' to avoid build time warnings. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-30libtool: Don't patch generated filesRichard Purdie1
We wipe out and regenerate all configure files so there is no point in patching them. 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>
2013-09-26gcc/libtool/perl: Fix various path to sed-native problemsRichard Purdie2
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] 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>
2013-09-17libtool: fix resolve of lt_sysrootHans Beckerus2
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 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>
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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-20 16:14:31 +0000