From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gettext_0.18.1.1.bb (PR r7 => r8)
Date: Wed, 14 Mar 2012 13:16:55 +0000 [thread overview]
Message-ID: <1331731015.18586.19.camel@ted> (raw)
In-Reply-To: <D9D7124626ED1E43963D86B2657D5CCD02EB625C@FRSNPREXC1.usr.ingenico.loc>
On Tue, 2012-03-13 at 16:00 +0100, Matthieu CRAPET wrote:
> Greetings,
>
> Updated my openembedded-core git repository.
> Rebuilt world for my custom distro (compiling for a BeagleBoard).
>
> I've got an error on gettext.
>
> .../build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-ing-linux-gnueabi/gcc/arm-ing-linux-gnueabi/4.6.4/ld: warning: library search path "/usr/lib" is unsafe for cross-compilation
> /usr/lib/libtinfo.so: file not recognized: File format not recognized
> collect2: ld returned 1 exit status
>
> Reintroducing --with-libncurses-prefix line solves the issue.
>
> Am I missing somthing here?
We've reverted the patch that caused this problem.
Cheers,
Richard
prev parent reply other threads:[~2012-03-14 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 15:00 gettext_0.18.1.1.bb (PR r7 => r8) Matthieu CRAPET
2012-03-14 13:16 ` 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=1331731015.18586.19.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox