summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/automake
Commit message (Collapse)AuthorAgeFilesLines
* automake-nativesdk: fix builds on fedora 17Robert Yang2012-04-161-3/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Generally distros keep perl at /usr/bin/perl Fedora 17 also has /bin/perl this causes automake-nativesdk build on such distros to put perl interpreter path in the perl scripts as /bin/perl But we set perl location for target as /usr/bin/perl This mismatch of perl path causes failure of rootfs image creation like this: | error: Failed dependencies: | /bin/perl is needed by automake-nativesdk-1.11.2-r2.x86_64 NOTE: package meta-toolchain-gmae-1.0-r7: task do_populate_sdk: Failed The second sed command is for such a case: eval 'case $# in 0) exec /bin/perl -S "$0";; *) exec /bin/perl -S "$0" "$@";; esac' This line has two "/bin/perl" and we can't use a line number to tell sed which line it is since the line numbers in different files are defferent. [YOCTO #2304] (From OE-Core rev: ee7a86c06c2289f01aa5f1da958ce51523495572) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Convert getVar/getVarFlag(xxx, 1) -> (xxx, True)Richard Purdie2012-03-051-1/+1
| | | | | | | | | | | | Using "1" with getVar is bad coding style and "True" is preferred. This patch is a sed over the meta directory of the form: sed \ -e 's:\(\.getVar([^,()]*, \)1 *):\1True):g' \ -e 's:\(\.getVarFlag([^,()]*, [^,()]*, \)1 *):\1True):g' \ -i `grep -ril getVar *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: omit compilation of pyc files on installAndreas Oberritter2012-02-262-2/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * On install, automake calls py-compile, which previously compiled python source code to pyc and pyo, which both got packaged. * The python interpreter in OE contains patches to enable optimization (pyo) by default: 04-default-is-optimized.patch 99-ignore-optimization-flag.patch * automake created pyc files by calling py_compile.compile() and adding the c suffix manually, resulting in identical byte code for both pyc and pyo files. * py-compile-compile-only-optimized-byte-code.patch applies to automake 1.11 and automake master, but older versions require a slightly modified patch. However, older versions are only pinned by chinook-compat and nylon, so I left them untouched. (From OE-Core rev: 40ccf816c597e7eed5243fb4b4e9473d2b58afaa) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> The patch was imported from the OpenEmbedded git server (git://git.openembedded.org/openembedded) as of commit id aa4585c5065e05c759f16e1e8623fc7f40640f1b. Modified to apply to automake version 1.11.2 and to include a patch header. Also renamed the patch. Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake-1.11.2: backport pkglibexec_SCRIPTS fixNitin A Kamble2012-01-062-2/+121
| | | | | | | | | | | | | automake-1.11.2 made variable libexec_SCRIPTS valid while pkglibexec_SCRIPTS invalid. Both should be either allowed or not allowed. This issue is fixed in the automake developement branch, and now backported into our automake 1.11.2 recipe. (From OE-Core rev: 4482675d3e3df3bcbedcf74eeeaec8bbc2af225a) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native.bbclass: Fix variable remapping coverageRichard Purdie2012-01-051-2/+3
| | | | | | | | | | | | | | | | | When looking for RDEPENDS to process, bitbake iterates through PACKAGES *and* PN. Since native.bbclass sets PACKAGES to be empty, its pointless remapping the list of PACKAGES since this does nothing. There is a problem since *_${PN} are used by bitbake but not remapped by the native.bbclass class extension code. This changes the code to remap _${PN} in both expanded and unexpanded forms. As a result of this, various surprising dependencies are uncovered and the patch rectifies those. These are real bugs since they're injecting unneeded (unremapped) dependencies into the dependency chain. (From OE-Core rev: 0f485bfd6fc82a109b9da629e464fca1e90faec3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: upgrade from 1.11.1 to 1.11.2Nitin A Kamble2012-01-032-3/+3
| | | | | | | (From OE-Core rev: 2dffe02af05413d8438ddc28d542dc5d85ac105f) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add Upstream-Status to patchesSaul Wold2012-01-031-0/+2
| | | | | | | (From OE-Core rev: 169e55d802883df763dbff4a4737e05e96358fa3) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: Extend to provide nativesdk recipeWenzong Fan2011-11-302-2/+3
| | | | | | | | | | | We will provide autotools nativesdk in meta-tookchain for reconfigure any autotools supported projects, as a part of the plan we should extend their recipes first. (From OE-Core rev: 2074285e84267f9f929ed6424f35cc4b2a00c335) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie2011-11-101-1/+1
| | | | | | | | | | | | | | | | | This is the result of running the following over the metadata: sed \ -e 's:bb.data.\(setVar([^,()]*,[^,()]*\), *\([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,()]*,[^,()]*,[^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^() ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` (From OE-Core rev: b22831fd63164c4db9c0b72934d7d734a6585251) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Delete patch=1, its default and replace pnum with striplevelKhem Raj2011-08-231-1/+1
| | | | | | | | | | Some place pnum=1 is used which is removed as well since striplevel=1 is default (From OE-Core rev: 4e108857e0d40105f7ecbc55e99bd6c367bb7386) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: Update for python.m4 to respect libdirKumar Gala2011-08-123-2/+63
| | | | | | | | | | | | As we tweak libdir we need python libs that utilize configure to respect it setting. By updating the python.m4 template, when we regen automake files they will than respect the setting of libdir which is standard for any autotools based recipe. (From OE-Core rev: d300cfe603b00fc963f7ed874563016fcbcc47a8) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: Fix issue with tar configure failing with large UID/GIDsKumar Gala2011-08-033-2/+44
| | | | | | | | | | | Add a fixup for trying to create ustar archives when the users UID or GID is larger than the format allows. (From OE-Core rev: 7a092818f901c5c860e82f573534cd505d9fb959) Signed-off-by: Tom Rini <tom_rini@mentor.com> Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf/automake: Bump PR to resolve perl-native issueSaul Wold2011-06-141-1/+1
| | | | | | | (From OE-Core rev: e7e00c4d8e86a90c19f553b35a62aa091b6ad14c) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Update upstream-status of patchesNitin A Kamble2011-05-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 (From OE-Core rev: a62fa9b213b09bf48c48499d2e3c66a9ee306deb) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes-devtools: Add Summary informationMark Hatle2010-12-161-1/+3
| | | | | | Add Summary information and update Descripts as necessary. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
* SRC_URI Checksums AdditionalsSaul Wold2010-12-091-0/+3
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* automake:Add license checksum to bb fileMei Lei2010-11-241-1/+2
| | | | | | Add COPYING file checksum to bb file Signed-off-by: Mei Lei <lei.mei@intel.com>
* Major layout change to the packages directoryRichard Purdie2010-08-273-0/+121
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>