From: Hans Beckerus <hans.beckerus@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: Adding prebuilt binaries to /usr/bin on rootfs
Date: Wed, 17 Apr 2013 21:10:36 +0200 [thread overview]
Message-ID: <516EF3AC.8060803@gmail.com> (raw)
In-Reply-To: <CAJTo0Laj1w=q5NSq+zpZufLib8gs2qOKkzQi2syVpjep13ML_Q@mail.gmail.com>
On 2013-04-17 8:54, Burton, Ross wrote:
> On 17 April 2013 19:10, Satya Swaroop Damarla <swaroop.damarla@gmail.com> wrote:
>> If I dont avoid this error.. I cant build the rootfilesystem....
> Hopefully someone else will respond who knows how to handle that problem.
I do not have a direct answer, but googling this problem seems to give a
lot of hits, with various answers on how to resolve it.
The common thing seems to be that they all cover binaries compiled from
within OE/Yocto. In this case I think we are talking pre-built binaries,
right?
The hash problem could (because I am not sure) be a combination of the
compiler being used, linker options and what Yocto expects.
Is it possible for you to recompile your binaries? In that case try to
add this switch to LDFLAGS (or whatever flags you use to feed the
linker), --hash-style=gnu. Also see http://lwn.net/Articles/192624/
I might be completely off-target here but take it for what it is ;)
Hans
next prev parent reply other threads:[~2013-04-17 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 15:00 Adding prebuilt binaries to /usr/bin on rootfs Satya Swaroop Damarla
2013-04-17 15:05 ` Burton, Ross
2013-04-17 15:11 ` Satya Swaroop Damarla
2013-04-17 15:56 ` Burton, Ross
2013-04-17 18:10 ` Satya Swaroop Damarla
2013-04-17 18:54 ` Burton, Ross
2013-04-17 19:10 ` Hans Beckerus [this message]
2013-04-18 5:01 ` Michael Fainstein
2013-04-19 6:10 ` Satya Swaroop Damarla
2013-04-26 5:55 ` Khem Raj
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=516EF3AC.8060803@gmail.com \
--to=hans.beckerus@gmail.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.