Bug#814702: ghostscript: FTBFS on sparc64 due to mismatched symbols file
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 02/15/2016 03:05 PM, Jonas Smedegaard wrote:
> Seems tied to Ghostscript and a deliberate change since 9.16:
>
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8a275b2
Awesome observation, thank you very much. I was looking through the
sources yesterday for a while but for some reason, this must have
slipped through. This answers my question perfectly! It's should
be therefore safe to make the symbol on sparc* optional since upstream
intends this behavior.
> I am not good at understanding symbols handling, so advice on how
> best to proceed is appreciated.
Just prepend this symbol with "(arch!=sparc arch!=sparc64)" so that
the line becomes:
(arch!=sparc arch!=sparc64) hdr_id@Base 9.10~dfsg
Cheers,
Adrian
- --
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWwd9jAAoJEHQmOzf1tfkTXy4P/0Ez7XxW7+ASRZIXXUOGSTw9
6X4ipUwTn1cVlMNhV3WuZLhc1gZvyHge6D5/s3Eaa1eV2VIRvoOro9w8Ebg1e3Yo
j33FajJbCSYMvnMQtk2c51d0J2pCgHKqyLN/2N/AKNyTdV0ncqyTh3yBe5nOjn9j
caoYzsYqAHTifib9ysxVExMKxqwcVPYv1rRBpYUH0+wLDRfCdyDUsRPzN9880Ld3
K67y1Q0JQI/GcliVUXXPv8RjIHp4KakdmgIjsETPhHC9bjLxbyJJsWd7lSW5mwUO
+Ar03g4SEYt8ia16yMGTP2EAkYUP2RnABRbXuFbvyBfS0FlIxjp5Equ0tgPdEE49
ALgus/cDUbLO+JzsfKySnq9bTcD64Z54yz3AQ+8+gnU943ywdUMJoK6nbX6dUFDK
EZ6N9Vm0hse/ELNKv8K6nHQrb6EIV0CyVGVh3zwNxFJm2UHM3fl6+g5tIZf3fJRn
v4IQPnmE2/rDL5CHODBJPm7nX0n8a4qEOTMXnAiUFzj3ukdMieBA0PDgduaLWtCF
zCL8k6rs7fod/r/Xw/HuOGRKZWmqgnTwxeheGUUQP+F1Zsp6568x7GYTb62TFqv+
fJEDs4WFRZcq8HrR+nmndo5nQOZjFUhE6Ilk0wm76Umdz6Y3kDryaBEJJX2Tt3xH
D/xYQLTpxgSX6jPPE1YX
=i3aq
-----END PGP SIGNATURE-----
Reply to: