Re: Ghostscript/GhostPDL 9.28 Release Candidate 1

Chris Liddell <[email protected]> Wed, 21 Aug 2019 14:30:29 +0100
Newsgroups gmane.comp.printing.ghostscript.devel
Message-ID <CAGy8pWpTk2KG0_CHJv9xcHcQX3xqECVYZ0Sd5O2m8dOLMpjezA@mail.gmail.com>
On Wed, 21 Aug 2019 at 13:47, Akira Kakuto <[email protected]> wrote:
>
> Dear Chris,
>
> > I worked on the assumption you were setting the path *somehow*, and in
> > debugging it, I noticed a problem with directory separators, which I fixed:
> >
> > http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=ec0b35fed3de
> >
> > I'm 90% sure that's the source of the problem you're seeing (especially
> > looking at the path for the font file above). This also explains why I
> > didn't see this in my testing, as I use Linux, where the OS and
> > Postcript directory separators are consistent with each other.
>
> Unfortunately the change does not improve my bad situations.

Well, I just followed the steps you've detailed in this thread; I
added your patch to nsisinst.nsi, built with COMPILE_INITS=0 and then
built the installer. Then I installed it in c:\usr\gs\gs9.28. I double
checked that the revised GS_LIB value was written to the registry.

Running the exe, I still get:
"GPL Ghostscript RELEASE CANDIDATE 1 9.28: Can't find initialization
file gs_init.ps."

So, I'm still not clear how you are getting this to work at all (note
that SAFER is activated in gs_init.ps, so if we can't find gs_init.ps,
it *cannot* be SAFER causing the problem).

Chris