I have returned to packaging lilypond with denemo and using it. The problem
may be how I have compiled either lilypond or ghostscript. I have edit the
denemo.sh file to not launch denemo but to launch gs. Here is what I get if
I do not set GS_LIB:

GPL Ghostscript 9.19: Can't find initialization file gs_init.ps.

If I set it and launch gs like this:

$PREFIX/bin/gs -sGenericResourceDir=$PREFIX/share/ghostscript/9.19/Resource


I get this:



File name
/Users/jbenham/Desktop/Denemo.app/Contents/MacOS/../Resources/share/ghostscript/9.19/Resource
cant combine with x/y

While reading gs_res.ps:

Error: /configurationerror in GenericResourceDir

Operand stack:

   (gs_typ42.ps\000gs_cidfn.ps\000gs_cidcm.ps\000gs_fntem.ps\000gs_cidtt.ps\
000gs_cidfm.ps\000gs_cmap.ps\000gs_setpd.ps\000gs_fapi.ps\000gs_typ32.ps\
000gs_frsd.ps\000gs_ll3.ps\000gs_icc.ps\000gs_mex_e.ps\000gs_mro_e.ps\
000gs_pdf_e.ps\000gs_wan_e.ps\000pdf...)   (gs_res.ps)   (x/y)   3   93

Execution stack:

   %interp_exit   --nostringval--   --nostringval--   %loop_continue
--nostringval--   --nostringval--   --nostringval--   false   1
%stopped_push   --nostringval--

Dictionary stack:

   --dict:807/1123(G)--   --dict:71/200(L)--   --dict:807/1123(G)--
--dict:169/251(G)--

Current file position is 12788

  ./base/gsicc_manage.c:1126: gsicc_open_search(): Could not find
default_gray.icc

| ./base/gsicc_manage.c:1754: gsicc_set_device_profile(): cannot find
device profile

Unrecoverable error: unknownerror in .special_op

Operand stack:


gs_typ42.psgs_cidfn.psgs_cidcm.psgs_fntem.psgs_cidtt.psgs_cidfm.psgs_cmap.psgs_setpd.psgs_fapi.psgs_typ32.psgs_frsd.psgs_ll3.psgs_icc.psgs_mex_e.psgs_mro_e.psgs_pdf_e.psgs_wan_e.pspdf_ops.psgs_l2img.pspdf_rbld.pspdf_base.pspdf_draw.pspdf_font.pspdf_main.pspdf_sec.psgs_cff.psgs_mgl_e.psgs_ttf.psgs_dps.psgs_dpnxt.psgs_epsf.psgs_pdfwr.ps
gs_res.ps  x/y  3  93

  ./base/gsicc_manage.c:1126: gsicc_open_search(): Could not find
default_gray.icc

+ ./base/gsicc_manage.c:2724: gs_setdefaultgrayicc(): cannot find default
gray icc profile

GPL Ghostscript 9.19: ERROR -1 reclaiming the memory while the interpreter
finalization.




On Fri, May 19, 2017 at 3:59 AM, Richard Shann <rich...@rshann.plus.com>
wrote:

> On Fri, 2017-05-19 at 09:58 +0000, Tony Ventura wrote:
> > Richard,
> > I did the following:
> > Attempt #1:
> > Opened your attached denemo.sh in TextEdit, copied the contents and
> > replaced the
> > orginal /Users/anthonyventura/Desktop/Denemo.app/Contents/MacOS/
> denemo.sh.
>
> > Attempting to launch in the Terminal did not work. Double-clicking on
> > the Denemo icon on my desktop did not work.
> [...]
> >
> > Lastly, I attached the terminal output of the first attempt, when
> > Denemo would not open.
>
> Well, it's different. The terminal output now shows that Denemo itself
> will not launch because the system is finding older versions of
> libraries. That will be because /usr/lib has been put in front of the
> location of the libraries shipped with Denemo, which are more recent.
> So I attach another denemo.sh which this time places /usr/lib after
> Denemo's versions.
>
> Jeremiah, I've just downloaded the official LilyPond release for MacOSX
> from
>
> http://download.linuxaudio.org/lilypond/binaries/darwin-
> x86/lilypond-2.18.2-1.darwin-x86.tar.bz2
>
> and from that it seems that the executable "lilypond" is a binary
> executable, not a shell script, so this recent Apple change to scrubbing
> environment variables before running bash does not apply. However, the
> change is IIUC a security measure applying to *all* executables that are
> protected by Apple. So perhaps the important difference is that the
> external LilyPond install is not on Tony's desktop but system-wide
> under /Applications. So perhaps it is protected from being run with
> environment variables set.
>
> Can you return to the internal LilyPond, so that complication is
> avoided?
>
> Richard
>
>
>
>
>
>
_______________________________________________
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Reply via email to