From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Subject: export TARGET_LDFLAGS and native sstate
Date: Mon, 7 Apr 2014 16:53:33 +0100 [thread overview]
Message-ID: <20140407155333.GA19351@mcrowe.com> (raw)
We're building for both ARM and MIPS-based MACHINEs in a single source
tree. This seems to result in us compiling (or luckily most of the time
resurrecting from sstate-cache) two different versions of all -native
packages due to different base hashes.
It seems that this difference in base hashes is due to the exported
variable TARGET_LDFLAGS being different between the two CPUs:
< export TARGET_LDFLAGS="-Wl,-O1 -Wl,--as-needed"
---
> export TARGET_LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
which in turn is because TARGET_LINK_HASH_STYLE is explicitly set to "sysv"
on MIPS but allowed to be "gnu" on everything else.
Every time I switch back and forth between building ARM-based and
MIPS-based machines the do_populate_sysroot_setscene tasks run for each
required -native recipe.
If I modify native.bbclass to do:
TARGET_LDFLAGS = "${BUILD_LDFLAGS}"
then the hashes match and this unnecessary sysroot population is avoided.
Is this a sensible thing to be doing? It does mean that TARGET_LDFLAGS
contains a lot of (presumably unnecessary) rpath shenanigans but perhaps
that doesn't matter. :(
Thanks.
Mike.
next reply other threads:[~2014-04-07 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 15:53 Mike Crowe [this message]
2014-04-07 16:17 ` export TARGET_LDFLAGS and native sstate Chris Larson
2014-04-07 16:49 ` Mike Crowe
2014-04-10 16:15 ` Mike Crowe
2014-04-10 17:36 ` Chris Larson
2014-04-10 17:38 ` Denys Dmytriyenko
2014-04-07 19:35 ` Khem Raj
2014-04-16 9:43 ` Mike Crowe
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=20140407155333.GA19351@mcrowe.com \
--to=mac@mcrowe.com \
--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 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.