[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#814702: ghostscript: FTBFS on sparc64 due to mismatched symbols file



Quoting John Paul Adrian Glaubitz (2016-02-15 15:23:38)
> -----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

Shouldn't it be this instead?:

(arch=!sparc,!sparc64)hdr_id@Base 9.16~dfsg

i.e. the folowing differences:

 * negating each value (not the equals sign)
 * comma-sepate values (or else pipe- (not space-)separate declarations)
 * limit to version 9.16 (when it was changed upstream

What do you think of that?

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


Reply to: