On Thu, Feb 02, 2017 at 06:23:57PM +0000, Ken Moffat wrote: > In a fresh system, ghostscript's 'make so' fails - several warnings > which seem to be unchanged from my last build in November, but then > > In file included from ./psi/dxmain.c:38:0: > ./psi/iapi.h:215:1: note: expected 'char **' but argument is of type 'const > char **' > gsapi_get_default_device_list(void *lib, char **list, int *listlen); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > make[2]: Leaving directory '/scratch/working/ghostscript-9.20' > make[1]: Leaving directory '/scratch/working/ghostscript-9.20' > > I'm way out of my depth on this, with no idea what changed. Any > suggestions, pretty please ? >
Sat scratching my head, looked all through the log from the beginning of 'make so' but couldn't see any errors only warnings. Added some instrumentation to shout $? to my log after each command, gave it anther try and this time it sailed through. Odd, but works for me. > Meanwhile, I looked at Arch - they don't seem to make so - and then > at Fedora : nothing there for this problem, but a whole string of > CVE fixes - some in the last few days, some earlier - for > CVE-2016-7976/7977/7978/7979/8602/9601 although not all applied in > that order. > > I am tempted to apply all of these as security fixes (assuming, for > the moment, that they do apply), but it doesn't look as if they will > solve my FTBFS so I'm stalled. > I intended to post this to -dev, maybe I'll take that there or maybe I'll just let it lie for the moment - it's not as if details of the issues are at Mitre yet, although redhat and debian seem to know about them. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
