Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: "openembedded-core@"
	<lists.openembedded.org.openembedded-core@lists.openembedded.org>
Subject: Suggestion: Occasionally take --hash-style=gnu out of the linker
Date: Thu, 31 May 2012 16:14:12 -0500	[thread overview]
Message-ID: <20120531161412.561acb04@wrlaptop> (raw)

It occurred to me:

In theory, it's a bug if a package is configured such that it does not
actually request hash-style=gnu.  In practice, though, the yocto
toolchain is configured so that it's the default.

Maybe there should be a periodic build or two that uses a compiler not
configured that way, to flush out such packages?

-s
-- 
Listen, get this.  Nobody with a good compiler needs to be justified.



             reply	other threads:[~2012-05-31 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 21:14 Peter Seebach [this message]
2012-05-31 21:20 ` Suggestion: Occasionally take --hash-style=gnu out of the linker 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=20120531161412.561acb04@wrlaptop \
    --to=peter.seebach@windriver.com \
    --cc=lists.openembedded.org.openembedded-core@lists.openembedded.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