From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lsof: Fix cross 32 -> 64bit ranlib host contamination problem
Date: Wed, 13 Jun 2012 11:43:03 +0100 [thread overview]
Message-ID: <1339584183.8065.25.camel@ted> (raw)
In-Reply-To: <1339537351-2918-1-git-send-email-jason.wessel@windriver.com>
On Tue, 2012-06-12 at 16:42 -0500, Jason Wessel wrote:
> When building on a 32bit host OS and building 64 bit binaries,
> the cross ar and ranlib must be called, or you get an error
> as follows:
>
> x86_64-wrs-linux-gcc -m64 --sysroot=/opt/build/tmp/sysroots/qemux86-64 -o lsof dfile.o dmnt.o dnode.o dproc.o dsock.o dstore.o arg.o main.o misc.o node.o print.o proc.o store.o usage.o util.o -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -L./lib -llsof
> ./lib/liblsof.a: could not read symbols: Archive has no index; run ranlib to add one
> collect2: error: ld returned 1 exit status
>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
> meta/recipes-extended/lsof/lsof_4.85.bb | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-06-13 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 21:42 [PATCH] lsof: Fix cross 32 -> 64bit ranlib host contamination problem Jason Wessel
2012-06-13 10:43 ` 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=1339584183.8065.25.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