From: Scott Garman <scott.a.garman@intel.com>
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: Tue, 25 Jan 2011 22:18:24 -0800 [thread overview]
Message-ID: <4D3FBCB0.1030609@intel.com> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F20A8339044@shsmsx502.ccr.corp.intel.com>
On 01/25/2011 09:56 PM, Lu, Lianhao wrote:
> Hi Scott,
>
> I'm wondering whether the grammar of the .la files generated by new
> libtool 2.4 is different from the old ones. Take the file
> libxcb-res.la generated by libxcb for example, it contains a line:
>
> dependency_libs=' =/usr/lib/libxcb.la =/usr/lib/libXau.la'
>
> While in the old libxcb.la file, this line appeared to be
>
> dependency_libs=' /usr/lib/libxcb.la /usr/lib/libxcb.la'
>
> Is the "=" a new grammar for liblool 2.4? Because in meta-toolchain,
> it needs to fix these .la files by replacing all the "/usr/lib" to
> "${SDKTARGETSYSROOT}/usr/lib", etc. This new "=" causes the original
> regular expression not work.
Hi Lianhao,
I'm not sure if the "=" grammar changed with Libtool 2.4 or not, as I
haven't spent any time digging into Libtool when we used 2.2 a while ago.
I do believe you will run into problems if you try to set
dependency_libs to =/usr/lib. The reason is that you should not be
adding system default directories to dependency_libs.
=${SDKTARGETSYSROOT}/usr/lib should be fine.
Where is the regular expression you're referring to above? Since Poky
has been using Libtool 2.4 for a while now (I simply enabled sysroot
support), I would think this error would have cropped up much earlier.
> b.t.w. Do we still need the code in meta-toolchain to fix broken .la
> files? According to my understanding, the new sysroot support in
> libtool 2.4 should solve this problem, right? Thanks!
Again, which code snippet are you referring to (file and line #,
please)? There are some changes I made to remove .la munging code, and
I'm pretty sure Richard reviewed it giving consideration to how it would
impact the meta-toolchain builds.
Once I have the code sections to examine we should be able to iron this
out more clearly.
Thanks,
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-01-26 6:18 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 [this message]
2011-01-26 6:39 ` Lu, Lianhao
2011-01-26 9:42 ` Richard Purdie
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=4D3FBCB0.1030609@intel.com \
--to=scott.a.garman@intel.com \
--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.