I see the problem with his lilypond. His lilypond seems to not be able to
find $PREFIX/share/ghostscript. I bet there is a command we can pass to
lilypond to tell it were it is.

Jeremiah

On Mon, May 15, 2017 at 6:05 AM, Tony Ventura <tonyventur...@verizon.net>
wrote:

> Not sure what I should do with this information.
>
> Today is a work day. My ability to respond in a timely fashion will be
> delayed.
>
> Please let me know next steps. The latest is that when I launch Denemo, I
> get a very small window with no menu, and no Lilypond preview. The only
> recourse is the force quit.
>
> Kind regards,
> Tony Ventura
> www.tonyventura.com
>
> <http://beachbodycoach.com/esuite/home/tonyvt/>
>
>
> On Monday, May 15, 2017 5:07 AM, Richard Shann <rich...@rshann.plus.com>
> wrote:
>
>
> On Sun, 2017-05-14 at 19:50 +0000, Tony Ventura wrote:
> > The following is where the Critical Messages start appearing.
> > Denemo - CRITICAL: No menu in core/menusystem.c
>
> ah, I didn't notice you attached the log showing what happened leading
> up to that error:
>
> Denemo - WARNING : Could not find palette file.
> Denemo - MESSAGE : Denemo version 2.1.0
> Denemo - WARNING : Unable to load default keymap
> Denemo - WARNING : Cannot find Denemo's scheme initialization file
> denemo.scm
>
>
> So that error is just a consequence of not finding the default keymap
> (or pretty much anything else).
> I see that Fluidsynth fails to initialize too, it complains that it
> can't find /proc/self/exe which is what you use on Unix to find where
> the executable that is running is located in the file system (I think)
> so this will be relevant:
>
> http://stackoverflow.com/questions/22675457/what-is-
> the-equivalent-of-proc-self-exe-on-macintosh-os-x-mavericks
>
> perhaps Denemo uses the same strategy to find the default palettes,
> Default.commands etc all the woes would flow from there.
>
>
> Richard
>
>
>
>
>
_______________________________________________
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Reply via email to