From: "Peter A. Bigot" <pab@pabigot.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: blocking pie in recipes that build shared object files
Date: Mon, 04 Aug 2014 09:56:37 -0500 [thread overview]
Message-ID: <53DF9F25.1060404@pabigot.com> (raw)
I've now hit two recipes in meta-openembedded that fail on armv7-a
because SECURITY_CFLAGS has -pie as an option that leaks into a link
command building a shared object file. This produces:
|
/prj/oe/omap/build-beaglebone-master/tmp/sysroots/beaglebone/usr/lib/Scrt1.o:
In function `_start':
|
/prj/oe/omap/build-beaglebone-master/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/eglibc/2.19-r0/eglibc-2.19/libc/csu/../ports/sysdeps/arm/start.S:128:
undefined reference to `main'
| collect2: error: ld returned 1 exit status
| error: command 'arm-poky-linux-gnueabi-gcc' failed with exit status 1
In openembedded-core meta/conf/distro/include/security_flags.inc
provides a bunch of package-specific overrides to use
SECURITY_NO_PIE_CFLAGS for this sort of package.
It's not clear to me how that should be accomplished for recipes that
are not part of openembedded-core. For
http://patches.openembedded.org/patch/77165/ for python-smbus in
meta-python I chose to override it in the bb file.
What is the best-practices solution to this problem?
Peter
next reply other threads:[~2014-08-04 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 14:56 Peter A. Bigot [this message]
2014-08-04 22:39 ` blocking pie in recipes that build shared object files Khem Raj
2014-08-05 9:31 ` Peter A. Bigot
2014-08-05 14:47 ` 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=53DF9F25.1060404@pabigot.com \
--to=pab@pabigot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox