<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/automake, branch 1.3</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=1.3</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=1.3'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2012-09-24T10:30:33+00:00</updated>
<entry>
<title>autotools: Remove special handling for autoconf* and automake*</title>
<updated>2012-09-24T10:30:33+00:00</updated>
<author>
<name>Phil Blundell</name>
<email>philb@gnu.org</email>
</author>
<published>2012-09-22T16:18:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=82a99a4cee4c63bafe6335897f2adccb5fe2a7c7'/>
<id>urn:sha1:82a99a4cee4c63bafe6335897f2adccb5fe2a7c7</id>
<content type='text'>
For reasons that are now shrouded in obscurity, autotools.bbclass
has long contained a special heuristic to avoid attempting to run
autoreconf when building autoconf or automake themselves.  However,
the wildcard test against PN which is used there is problematic when
trying to build another package whose name happens to start with
"autoconf", and in any case it is silly to do this test at runtime
for every package.  The individual recipes for autoconf and automake
can just as easily suppress the behaviour that they don't want by
providing a custom do_configure() method which just runs configure.

(From OE-Core rev: a87db6f8dea71cbb7ead9285ff8af0e28cf75604)

Signed-off-by: Phil Blundell &lt;pb@pbcl.net&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>automake: upgrade to 1.12.3</title>
<updated>2012-09-04T11:53:03+00:00</updated>
<author>
<name>Constantin Musca</name>
<email>constantinx.musca@intel.com</email>
</author>
<published>2012-09-03T07:06:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e7b20fa79cde18587e6994c3854080cae7cd4d24'/>
<id>urn:sha1:e7b20fa79cde18587e6994c3854080cae7cd4d24</id>
<content type='text'>
(From OE-Core rev: 1110da87a2395e1d516f092553e6ed542bb34805)

Signed-off-by: Constantin Musca &lt;constantinx.musca@intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>nativesdk: Switch to using nativesdk as a prefix, not a suffix</title>
<updated>2012-09-02T12:52:06+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-12-22T17:43:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ad23395cd1f6c0cbfcc6980b6071d589f9f6cde0'/>
<id>urn:sha1:ad23395cd1f6c0cbfcc6980b6071d589f9f6cde0</id>
<content type='text'>
As discussed on the mailing lists, using a suffix to package names is
hard and has lead to many recipes having to do PKGSUFFIX games. Its
looking extremely hard to scale nativesdk much further without hacking
many recipes.

By comparison, using a prefix like multilib does works much better and
doesn't involve "hacking" as many recipes. This change converts nativesdk
to use a prefix using the existing multilib infrastructure.

(From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>automake: Fix version reference in path substitutions</title>
<updated>2012-08-07T22:36:05+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2012-08-07T22:34:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=87ffccb5dc184375e8807834e3b9b08ada708105'/>
<id>urn:sha1:87ffccb5dc184375e8807834e3b9b08ada708105</id>
<content type='text'>
Without this the substitutions don't get made potentially resulting in a variety of
different failures.

(From OE-Core rev: 1e873271362b770381903098d46c4aec164d81de)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake.conf: Define USRBINPATH globally instead of individually</title>
<updated>2012-07-18T21:18:52+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2012-07-18T17:38:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ac7a0311825e20c544d17bfd8be63546ad36e665'/>
<id>urn:sha1:ac7a0311825e20c544d17bfd8be63546ad36e665</id>
<content type='text'>
Many recipes are now having to define PERLPATH and PYTHONPATH variables.
Creating USRBINPATH in bitbake.conf means we can remove all these lines
from the many recipes now needing this and simplify the code changes
needed in each case, reducing the chance of errors being introduced.

Also fixup glib python binary location issue and fix function indentation.

(From OE-Core rev: cf63d9068c3a8c635dfc240d30dfff278be9b0e2)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>automake: upgrade from 1.11.3 to 1.12.1</title>
<updated>2012-07-17T09:54:03+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2012-07-05T12:18:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bf6786ba6329c3bd920280006720ebc3db115ec6'/>
<id>urn:sha1:bf6786ba6329c3bd920280006720ebc3db115ec6</id>
<content type='text'>
(From OE-Core rev: c6b70eff7614ea774c0d8e39520f76bdce0ed977)

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>automake: upgrade from 1.11.2 to 1.11.3</title>
<updated>2012-04-26T09:05:06+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2012-03-16T19:00:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9f17530dcc82783ab039a34e92fc6f67487fd2dd'/>
<id>urn:sha1:9f17530dcc82783ab039a34e92fc6f67487fd2dd</id>
<content type='text'>
Removed already upstream patch:
  automake/automake_1.11.2_fix_for_pkglibexec_SCRIPTS.patch

Rebased these patches to the newer code:
  automake/prefer-cpio-over-pax-for-ustar-archives.patch
  automake/python-libdir.patch

Changed the tarball name from bz2 to gz, as the bz2 tar ball
is not published for the 1.11.3 version.

[RP: Fix python.m4 to preserve the tweaks that allow us to build python modules]
(From OE-Core rev: 94bf72aeae035ffade75bd9343937888bbb09c82)

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>automake-nativesdk: fix builds on fedora 17</title>
<updated>2012-04-16T21:53:00+00:00</updated>
<author>
<name>Robert Yang</name>
<email>liezhi.yang@windriver.com</email>
</author>
<published>2012-04-16T09:18:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b6cbf1e48c6ba3a0353f4ee71c43292587210ca5'/>
<id>urn:sha1:b6cbf1e48c6ba3a0353f4ee71c43292587210ca5</id>
<content type='text'>
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 &lt;liezhi.yang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta: Convert getVar/getVarFlag(xxx, 1) -&gt; (xxx, True)</title>
<updated>2012-03-05T18:22:56+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2012-03-03T10:59:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=06f2f8ce0a3093973ca54b48f542f8485b666079'/>
<id>urn:sha1:06f2f8ce0a3093973ca54b48f542f8485b666079</id>
<content type='text'>
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 &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>automake: omit compilation of pyc files on install</title>
<updated>2012-02-26T11:42:34+00:00</updated>
<author>
<name>Andreas Oberritter</name>
<email>obi@opendreambox.org</email>
</author>
<published>2012-02-25T01:19:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=eb8ce05d1315110bb1d297dcd4971edf3a54ca9a'/>
<id>urn:sha1:eb8ce05d1315110bb1d297dcd4971edf3a54ca9a</id>
<content type='text'>
* 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 &lt;obi@opendreambox.org&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;

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 &lt;obi@opendreambox.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
