From: Khem Raj <raj.khem@gmail.com>
To: Jack Mitchell <ml@embed.me.uk>, "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: libtool --with-libtool-sysroot
Date: Wed, 16 Nov 2016 09:22:47 -0800 [thread overview]
Message-ID: <22d481e0-2b32-2959-522f-0ed7dbf71889@gmail.com> (raw)
In-Reply-To: <977eace4-b716-70f8-c9f3-837f0b6c239a@embed.me.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1193 bytes --]
On 11/16/16 2:20 AM, Jack Mitchell wrote:
> On 11/11/16 17:33, Burton, Ross wrote:
>>
>> On 11 November 2016 at 17:31, Jack Mitchell <ml@embed.me.uk
>> <mailto:ml@embed.me.uk>> wrote:
>>
>> How would one check which libtool was being used, or influence which
>> one autotools chooses?
>>
>>
>> One common problem is a makefile or configure using "libtool" directly
>> instead of $(LIBTOOL).
>>
>> Grep the generated Makefiles for "libtool", the only instance where it
>> is executed should be in an assignment to LIBTOOL. For example, glib:
>>
>> LIBTOOL = $(top_builddir)/x86_64-poky-linux-libtool
>>
>
> I got to the bottom of this, I was switching between native and cross
> compiling but only running 'autoreconf -i' so it was detecting libtool was
> already present from previous native runs and not replacing it with our
> 'cross' version of libtool. I feel like there should be a binary compatibility
> check in there to auto overwrite if they don't match, but hey ho.
>
> Always use autoreconf -if to force update of all the required autotools
> scripts in future.
what us autotools bbclass doing in this case ?
>
> Cheers,
> Jack.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-11-16 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 14:34 libtool --with-libtool-sysroot Jack Mitchell
2016-11-11 15:34 ` Burton, Ross
2016-11-11 17:31 ` Jack Mitchell
2016-11-11 17:33 ` Burton, Ross
2016-11-16 10:20 ` Jack Mitchell
2016-11-16 17:22 ` Khem Raj [this message]
2016-11-16 17:26 ` Burton, Ross
2016-11-16 17:28 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22d481e0-2b32-2959-522f-0ed7dbf71889@gmail.com \
--to=raj.khem@gmail.com \
--cc=ml@embed.me.uk \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox