diff options
author | Sergei Trofimovich <slyfox@gentoo.org> | 2018-09-18 23:51:44 +0100 |
---|---|---|
committer | Sergei Trofimovich <slyfox@gentoo.org> | 2018-09-18 23:51:44 +0100 |
commit | 81f0f5079c3200f32cb9f0a40589ab1ac48be82c (patch) | |
tree | 62d68904b4de30ff2b1a713ede2403a593a525b4 /app-text/ghostscript-gpl | |
parent | dev-util/spirv-tools: Require newer spirv-headers (diff) | |
download | gentoo-81f0f5079c3200f32cb9f0a40589ab1ac48be82c.tar.gz gentoo-81f0f5079c3200f32cb9f0a40589ab1ac48be82c.tar.bz2 gentoo-81f0f5079c3200f32cb9f0a40589ab1ac48be82c.zip |
sys-devel/crossdev: bump up to 20180918
Single new patch:
https://gitweb.gentoo.org/proj/crossdev.git/commit/?id=a23e6057c94403e010a4ccd06091b59cc332e593
"""
crossdev: don't enable USE=pie by default on any bare-metal targets
Unfortunately embedded world has a long way to go
to adopt --enable-default-pie as a first class citizen.
Note:
--enable-default-pie enabled two things:
- PIC-friendly code generation (-fPIE)
- PIE executables (-pie)
Normally one would expect firmware to pass compiler modes explicitly
to gcc: -fPIC (or -mauto-pic, -fno-PIC), -ffreestanding, -nostdlib.
Unfortunately upstreams are frequently reluctant to explicitly specify
new moving parts available in gcc (in this case -no-pie) and expect
gcc to behave as it used to in the world before --enable-default-pie.
Unfortunate but not entirely unreasonable.
Disable --enable-default-pie until user explicitly requests USE=pie.
"""
Reported-by: Bertrand Jacquin
Reported-by: sklv
Bug: https://lists.gnupg.org/pipermail/gnuk-users/2018-August/000086.html
Bug: https://github.com/gl-sergei/u2f-token/issues/14
Package-Manager: Portage-2.3.49, Repoman-2.3.10
Diffstat (limited to 'app-text/ghostscript-gpl')
0 files changed, 0 insertions, 0 deletions