Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Peter A. Bigot" <pab@pabigot.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: armv6k support in OE for raspberrypi and s3c6410
Date: Sat, 30 Aug 2014 08:49:25 +0100	[thread overview]
Message-ID: <1409384965.29296.214.camel@ted> (raw)
In-Reply-To: <540148D5.2040808@pabigot.com>

On Fri, 2014-08-29 at 22:45 -0500, Peter A. Bigot wrote:
> Unlike normal builds of a gcc toolchain, OE builds the runtime libraries 
> separately in gcc-runtime and using the machine's tuning flags which 
> include the architecture.  The flags affect how atomic operations are 
> implemented in the libraries.

Which are you trying to fix? The on target gcc or the SDK one?

In the SDK case, we have environment files which do explicitly specify
the compiler flags.

On target is harder however the on target gcc is compiled to a specific
PACKAGE_ARCH so we should be able to put specific tuning into that gcc.
It does sound like the changes to gcc-configure-common.inc were not the
way to resolve this though, I'd misunderstood what the patches were
doing.

Can we fix this by adjusting gcc itself (the on target version)?

Its even a very old bug:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=139

but we've not actually hit issues due to this before or at least they've
not been reported in these terms.

Cheers,

Richard



  reply	other threads:[~2014-08-30  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30  3:45 armv6k support in OE for raspberrypi and s3c6410 Peter A. Bigot
2014-08-30  7:49 ` Richard Purdie [this message]
2014-08-30 12:26   ` Peter A. Bigot
2014-08-30 16:54   ` Peter A. Bigot

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=1409384965.29296.214.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pab@pabigot.com \
    /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