diff options
author | jmmv <jmmv@FreeBSD.org> | 2015-11-09 04:09:59 +0800 |
---|---|---|
committer | jmmv <jmmv@FreeBSD.org> | 2015-11-09 04:09:59 +0800 |
commit | 209f7c5354459954440d5b07f02aab172650841d (patch) | |
tree | 4f057637df17829ca8031c2f30a223ba06c28582 /multimedia/py-guessit | |
parent | d8b309c535d1ee8b89cc03c536ec8a0b1fe326e9 (diff) | |
download | freebsd-ports-gnome-209f7c5354459954440d5b07f02aab172650841d.tar.gz freebsd-ports-gnome-209f7c5354459954440d5b07f02aab172650841d.tar.zst freebsd-ports-gnome-209f7c5354459954440d5b07f02aab172650841d.zip |
Add a MULTILIB option to gcc{,48,49,5} for powerpc64
This change is the same as r400632, which updated gcc[56]-devel, but now
for gcc{,48,49,5}. Waited a week to ensure the change caused nothing to go
horribly wrong but this change is very low risk because it only affects
powerpc64.
This fixes the build of gcc{,48,49,5} under powerpc64 when the system
is built without the lib32 libraries.
More in detail:
If the system is built with lib32 support (WITH_LIB32, which is the default),
building gcc from ports results in a compiler that can target both 64-bit and
32-bit binaries on powerpc64. However, when lib32 support is disabled
(WITHOUT_LIB32), gcc should only be built with 64-bit support or otherwise
the build fails.
To fix this, explicitly disable 32-bit support when /usr/lib32 is not present
and add a MULTILIB option (which is only defined for powerpc64 when 32-bit
support is possible and defaults to yes to preserve the current behavior) to
allow the user to explicitly control this feature.
Approved by: gerald (maintainer), bdrewery (mentor), andreast
Differential Revision: https://reviews.freebsd.org/D3952
Diffstat (limited to 'multimedia/py-guessit')
0 files changed, 0 insertions, 0 deletions