From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Lu, Lianhao" <lianhao.lu@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Is the grammar of .la files changed in new libtool 2.4?
Date: Wed, 26 Jan 2011 09:42:50 +0000 [thread overview]
Message-ID: <1296034970.27814.2181.camel@rex> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F20A8339088@shsmsx502.ccr.corp.intel.com>
On Wed, 2011-01-26 at 14:39 +0800, Lu, Lianhao wrote:
> Garman, Scott A wrote on 2011-01-26:
> The code snippet I mentioned about fixing broken .la files is in
> function do_populate_sdk() in file
> meta/recipies-core/meta/meta-toolchina.bb, you might search for "# Fix
> or remove broken .la files" to locate the code.
We should just be able to drop that now.
> > Once I have the code sections to examine we should be able to iron
> > this out more clearly.
> >
>
> I have one more question about how to use the new libtool (sysroot
> enabled libroot 2.4) in meta-toolchain. Is there anything missing in
> the following sequence(takes mips as example)? Thank you!
>
> $libtoolize --automake
> $aclocal -I <m4 dir containing m4 files from libtool 2.4>
> $autoconf
> $autoheader
> $automake -a
> $./configure --host=mips-poky-linux --target=mips-poky-linux --with-libtool-sysroot=<mips sysroot dir>
This looks correct off the top of my head, the important bit is the
libtoolize call and the specification of the libtool sysroot to
configure. I'm assuming libtoolize is from libtool-nativesdk?
Cheers,
Richard
next prev parent reply other threads:[~2011-01-26 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 5:56 Is the grammar of .la files changed in new libtool 2.4? Lu, Lianhao
2011-01-26 6:18 ` Scott Garman
2011-01-26 6:39 ` Lu, Lianhao
2011-01-26 9:42 ` Richard Purdie [this message]
2011-01-26 6:43 ` Khem Raj
2011-01-26 9:40 ` Richard Purdie
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=1296034970.27814.2181.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=lianhao.lu@intel.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.