From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libpcre not compiling
Date: Mon, 14 Feb 2011 16:50:57 +0100 [thread overview]
Message-ID: <4D594F61.4010700@vollmann.ch> (raw)
In-Reply-To: <09D9BE2AC4AA764DABAA8C91E48D819E011A8B5ACA@DEMCHP99E35MSX.ww902.siemens.net>
On 02/14/11 11:43, Aeschbacher, Fabrice wrote:
> I already reported that libpcre (7.6-r8) does not compile in released version 2010.12 :
>
> | /bin/grep: /usr/lib/libstdc++.la: No such file or directory
> | /srv/oe-2010/build/at91sam9g20ek/sysroots/x86_64-linux/usr/bin/sed: can't read /usr/lib/libstdc++.la: No such file or directory
> | arm-angstrom-linux-gnueabi-libtool: link: `/usr/lib/libstdc++.la' is not a valid libtool archive
>
> Now I just figured out that neither does gnutls-2.10.2-r10.1 :
>
> | /srv/oe-2010/build/at91sam9g20ek/sysroots/x86_64-linux/usr/bin/sed: can't read /usr/lib/libstdc++.la: No such file or directory
> | arm-angstrom-linux-gnueabi-libtool: link: `/usr/lib/libstdc++.la' is not a valid libtool archive
>
> This seems to be pretty much the same issue.
> Any idea?
These are not -native packages, correct?
Then libtool shouldn't look for /usr/lib/libstdc++.la.
I have the feeling that something in the libtool setup is wrong.
Regards,
Detlef
next prev parent reply other threads:[~2011-02-14 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 16:15 libpcre not compiling Aeschbacher, Fabrice
2011-01-27 19:01 ` Khem Raj
2011-01-28 8:06 ` Aeschbacher, Fabrice
2011-02-14 10:43 ` Aeschbacher, Fabrice
2011-02-14 13:10 ` Aeschbacher, Fabrice
2011-02-14 15:50 ` Detlef Vollmann [this message]
2011-02-14 17:05 ` Aeschbacher, Fabrice
2011-01-28 8:12 ` Aeschbacher, Fabrice
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=4D594F61.4010700@vollmann.ch \
--to=dv@vollmann.ch \
--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.