denemo-devel
[Top][All Lists]
Advanced

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

[Denemo-devel] Fwd: Re: Today's download: Tues 13 Feb appears to be brok


From: Jeremiah Benham
Subject: [Denemo-devel] Fwd: Re: Today's download: Tues 13 Feb appears to be broken
Date: Thu, 8 Mar 2018 09:33:47 -0600

Do you know how to set the path in Windows? 
I know it is something like
set PATH=C:

my question is is it comma seperated or what?

Jeremiah
---------- Forwarded message ----------
From: "Jeremiah Benham" <address@hidden>
Date: Mar 8, 2018 9:31 AM
Subject: Re: [Denemo-devel] Today's download: Tues 13 Feb appears to be broken
To: "richard" <address@hidden>
Cc:

There is a new snapshot created. It still has the same problems. It says something about lilypond exited with an error. I remember having the same problem is mac os X. I am going to look at the denemo.sh file I created for os x to see what I needed to do. I am pretty sure I had to set some environment variables because lilypond was not finding ghostscript causing it to crash. Lilypond works fine at the command line. It has to be an environment issue. 

I think I said that this was a 64 bit build. I think I was wrong. I think the default build in mxe is 32 bit. I am testing ot on a 64 bit windows version 7 running im virtualbox.

Jeremiah 

On Mar 3, 2018 3:12 AM, "Richard Shann" <address@hidden> wrote:
On Fri, 2018-03-02 at 13:39 -0600, Jeremiah Benham wrote:
>
>
> On Mar 2, 2018 9:24 AM, "Richard Shann" <address@hidden>
> wrote:
> On Thu, 2018-03-01 at 15:02 -0600, Jeremiah Benham wrote:
> > I have been unable to upload to git so I created a patch for
> > configure.ad so that when --enable-debug is added to prepends
> CFLAGS
> > -O0 -g
>
> Did you intend to include the patch? What is stopping you updating
> git?
>
> I am not sure. It is the same key. It is on a completely different
> key. Maybe it is to old or something. I may have to make a new one.
> There my be a problem with the file triplet uploading to ftp as well.
> I will try again soon or make a nee key. Didn't you have a similar
> issue?

I think my problem is that I changed the name of my localhost on
installing the new version of Debian

>  How did you resolve it?
I went to the Savannah interface and added my key https://savannah.gnu.
org/my/admin/
under Authentication Setup as I recall...


>  Here is that patch. You can apply and upload it if you wish:
> http://denemo.org/~jjbenham/mxe/src/denemo-1-autoconf.patch

I've pushed this to git, partly to check that the access is still ok
for me. Let me know when you have something new built to check.

Richard


reply via email to

[Prev in Thread] Current Thread [Next in Thread]