All of lore.kernel.org
 help / color / mirror / Atom feed
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:40:23 +0000	[thread overview]
Message-ID: <1296034823.27814.2169.camel@rex> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F20A8339044@shsmsx502.ccr.corp.intel.com>

On Wed, 2011-01-26 at 13:56 +0800, Lu, Lianhao wrote:
> 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?

Its new, yes and means that the path needs to be prefixed by the
sysroot. Libtool will add that prefix itself automatically if there is a
sysroot set.

>  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.

The = should replace the need to make this replacement.

> 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!

Correct.

We just have to ensure that libtool 2.4 with fixed sysroot support is
being used (libtool-nativesdk has the fixes).

Cheers,

Richard



      parent reply	other threads:[~2011-01-26  9:40 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
2011-01-26  6:43 ` Khem Raj
2011-01-26  9:40 ` Richard Purdie [this message]

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=1296034823.27814.2169.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.