On Tue, Feb 07, 2012 at 02:47:28PM -0800, Khem Raj wrote:
On (07/02/12 10:31), Mike Crowe wrote:
On Thu, Nov 17, 2011 at 12:13:25AM +, Richard Purdie wrote:
We should be using libtool-cross for cross compiling but
were not. This patch sets datadir so libtoolize ends up
containing
On Thu, Nov 17, 2011 at 12:13:25AM +, Richard Purdie wrote:
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.
I have a recipe that no longer works after this (or perhaps
On (07/02/12 10:31), Mike Crowe wrote:
On Thu, Nov 17, 2011 at 12:13:25AM +, Richard Purdie wrote:
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.
I have a recipe
Dear Richard,
Am Donnerstag, den 17.11.2011, 00:13 + schrieb Richard Purdie:
unfortunately I could not find the meaning of upbreak here.
We should be using libtool-cross for cross compiling but
were not.
Is that just a cosmetic thing or did packages break?
This patch sets datadir so
On Thu, 2011-11-17 at 10:08 +0100, Paul Menzel wrote:
Dear Richard,
Am Donnerstag, den 17.11.2011, 00:13 + schrieb Richard Purdie:
unfortunately I could not find the meaning of upbreak here.
Sorry, its a typo and should be unbreak
We should be using libtool-cross for cross compiling
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.
