From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: libtool woes
Date: Fri, 09 Jan 2015 11:26:44 -0700 [thread overview]
Message-ID: <54B01D64.4000101@mlbassoc.com> (raw)
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?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2015-01-09 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 18:26 Gary Thomas [this message]
2015-01-09 18:57 ` libtool woes Mark Hatle
2015-01-09 19:55 ` Gary Thomas
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=54B01D64.4000101@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.