All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Snyder <jay.snyder@tycoelectronics.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Openembedded-devel Digest, Vol 43, Issue 99
Date: Tue, 23 Feb 2010 08:45:01 -0500	[thread overview]
Message-ID: <4B83DBDD.7020004@tycoelectronics.com> (raw)
In-Reply-To: <mailman.5.1266922802.8892.openembedded-devel@lists.openembedded.org>

>
>
> The most easy way to turn it off is to not build with GNU HASH style, 
> This can
> be made by not using "--hash-style=SOMETHING" in the LDFLAGS.
>
> The GNU HASH is not a security mechanism but a dynamic linker 
> optimization to
> be able to resolve symbols faster.
>
> It was added later as the feature is not that old. Everything I do 
> build is
> building fine, so in case you see an "awful" lot of breakage it would 
> be nice
> if you could clarify this.
>
I'll post details next time I run into it.     Your solution above 
doesn't fix the problem, as the error the OE build system complaining 
about binaries NOT having the GNU Hash.      There are many packages 
that do not pass the "--hash-style" option from the bitbake configure 
task down to all their makefiles.    I'd have to go back through my 
local copies of recipes that I've patched to see which ones that I've 
had to do "CCFLAGS += ${LDFLAGS}" fix to.   In some cases, I needed to 
put patches in for Makefile.ac files.     Due to the current time crunch 
that I'm in on my current project, I will not have time for several 
weeks to go back through these changes.     It is my  intention to 
submit these patches for inclusion in OE when I have time (if someone 
else hasn't already).

Thank you,
Jay



       reply	other threads:[~2010-02-23 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1266922802.8892.openembedded-devel@lists.openembedded.org>
2010-02-23 13:45 ` Jay Snyder [this message]
2010-02-23 15:25   ` Openembedded-devel Digest, Vol 43, Issue 99 Holger Hans Peter Freyther
2010-02-23 13:51 ` How to build g++ to run on target? Jay Snyder
2010-02-23 18:12   ` Khem Raj
2010-02-23 22:37   ` Philip Balister
2010-02-23 23:09     ` Khem Raj
2010-02-24  0:53       ` Philip Balister
2010-02-24  1:06         ` Tom Rini
2010-02-24  2:33           ` Khem Raj
2010-02-24  3:08             ` Denys Dmytriyenko
2010-02-24  4:01               ` Khem Raj
2010-02-24  8:57           ` Martyn Welch

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=4B83DBDD.7020004@tycoelectronics.com \
    --to=jay.snyder@tycoelectronics.com \
    --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.