All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: libtool woes
Date: Fri, 09 Jan 2015 12:55:29 -0700	[thread overview]
Message-ID: <54B03231.6000807@mlbassoc.com> (raw)
In-Reply-To: <54B02496.5070409@windriver.com>

On 2015-01-09 11:57, Mark Hatle wrote:
> On 1/9/15 12:26 PM, Gary Thomas wrote:
>> I'm trying to build a recipe which uses libtool.  The problem
>> I'm having is that the program uses glib-2.0 and one of the
>> libraries from that package has library dependencies.  This
>> is giving libtool major troubles.  I get errors like this:
>>     | sed: can't read =/usr/lib/libffi.la: No such file or directory
>>     | libtool: link: `=/usr/lib/libffi.la' is not a valid libtool archive
>>
>> This is coming from libgobject-2.0.la which contains this line:
>>     dependency_libs=' =/usr/lib/libglib-2.0.la -lpthread -L=/usr/lib =/usr/lib/libffi.la'
>>
>> The odd thing is that my recipe built the last time I tried,
>> but admittedly that was in late 2013.
>>
>> Any ideas what I might be doing wrong or how to fix this?
>
> The version of libtool you are running doesn't understand cross compilation
> (sysroot) paths.  (Sysroot paths start w/ the '='.)  You should use "libtoolize"
> prior to running to update the libtool configuration to match the changes that
> OE/YP have.  This works in almost all cases.. (where it doesn't work usually
> means someone had manually hacked on the previous libtool file...)

Thanks, that fixed it.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2015-01-09 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 18:26 libtool woes Gary Thomas
2015-01-09 18:57 ` Mark Hatle
2015-01-09 19:55   ` Gary Thomas [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=54B03231.6000807@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@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.