From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: failure building opkg-native on 64 bit Ubuntu
Date: Sat, 15 May 2010 17:40:47 +0200 [thread overview]
Message-ID: <hsmf9v$mug$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTinydII_uSb0INtCwN6oo4nBu3oYkhKG4ZCr71Uj@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15-05-10 17:09, Steve Sakoman wrote:
> On Sat, May 15, 2010 at 7:38 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
>
>> On 15-05-10 15:41, Steve Sakoman wrote:
>>
>>>>> x86_64-linux-libtool: link: cannot find the library `' or unhandled
>>>>> argument `/..//lib'
>>>>> make[2]: *** [libopkg.la] Error 1
>>
>> Could you have a look at libcurl.la in your x86_64 sysroots dir? I
>> suspect that has the offending '/..//lib' in it.
>
> Yes, libcurl.la did contain the offending '/..//lib'
>
>> After removing that things build again for me. I suspect the curl-native
>> recipe installs a broken .la file.
>
> That worked for me too. Seems that we are plagued by broken .la files!
Indeed, luckily it was lib*c*url.la instead of libzurl.la, it happened
to be the 3rd one I checked :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL7sB/MkyGM64RGpERAjtgAKChAzQs1dJvcRbIhmuAVzl7kjGKYwCfSJcE
7PwgjTs238QFouPpw2Y1A3w=
=Xjrl
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-05-15 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 3:43 failure building opkg-native on 64 bit Ubuntu Steve Sakoman
2010-05-15 6:17 ` Khem Raj
2010-05-15 13:41 ` Steve Sakoman
2010-05-15 14:38 ` Koen Kooi
2010-05-15 15:09 ` Steve Sakoman
2010-05-15 15:40 ` Koen Kooi [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='hsmf9v$mug$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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.