2018-02-06 13:17 GMT+01:00 James Lowe :
> Hello,
>
> On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley
> wrote:
>
>> Hi,
>>
>> I'm still trying to get make doc work again for my guilev2 setup.
>> It now fails at a point I'm not able to surely track down.
>>
>> The only suspicious in the log I'm po
Hello,
On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley
wrote:
> Hi,
>
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
>
> The only suspicious in the log I'm pointed to is:
>
> Processing `./15/lily-ef5769c9.ly'
2018-02-05 23:59 GMT+01:00 Thomas Morley :
> 2018-02-05 23:48 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>>
Uh, you are aware that your log ends with:
Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core
2018-02-05 23:48 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>
>>>
>>> Uh, you are aware that your log ends with:
>>>
>>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>>
>>> The programming errors are a nuisance
Thomas Morley writes:
> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>
>>
>> Uh, you are aware that your log ends with:
>>
>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>
>> The programming errors are a nuisance (and should likely get fixed) but
>> this aborts for
2018-02-05 23:23 GMT+01:00 David Kastrup :
>
> Uh, you are aware that your log ends with:
>
> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>
> The programming errors are a nuisance (and should likely get fixed) but
> this aborts for entirely different reasons.
Yes,
Thomas Morley writes:
> Hi,
>
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
>
> The only suspicious in the log I'm pointed to is:
>
> Processing `./15/lily-ef5769c9.ly'
> Parsing...
> Renaming input to: `modifying-
Hi,
I'm still trying to get make doc work again for my guilev2 setup.
It now fails at a point I'm not able to surely track down.
The only suspicious in the log I'm pointed to is:
Processing `./15/lily-ef5769c9.ly'
Parsing...
Renaming input to: `modifying-the-ottava-spanner-slope.ly'
Interpreting
On 16-03-2016 22:58, Carl Sorensen wrote:
LilyPond can be very finicky trying to get a clean build. That's why we
recommend using LilyDev.
Thanks for that advice, though it is way beyond my skill and needs. I
never build anything else than current master, but have tried doing so
even back
Villum,
On 09/03/16 11:02, Villum Sejersen wrote:
- Original Message - From: "Villum Sejersen"
To: Sent: Wednesday, March 09, 2016 9:52 AM Subject:
make doc fails after updating dev to VERSION 2.19.38
While make [all] and make install repeatably works as usual from
- Original Message - From: "Villum Sejersen"
To: Sent: Wednesday, March 09, 2016 9:52 AM Subject:
make doc fails after updating dev to VERSION 2.19.38
While make [all] and make install repeatably works as usual from
latest git sources, make doc does not compile t
Villum Sejersen writes:
> While make [all] and make install repeatably works as usual from
> latest git sources, make doc does not compile the 2.19.38 version,
> regardless how many, how many times and which cleaning attempts I try
> before.
>
> Tanks in advance for any advice...
sudo apt-get in
- Original Message -
From: "Villum Sejersen"
To:
Sent: Wednesday, March 09, 2016 9:52 AM
Subject: make doc fails after updating dev to VERSION 2.19.38
While make [all] and make install repeatably works as usual from latest
git sources, make doc does not compile the 2.19.
While make [all] and make install repeatably works as usual from latest
git sources, make doc does not compile the 2.19.38 version, regardless
how many, how many times and which cleaning attempts I try before.
The last few lines of the log file looks:
mkdir -p ./out-www
touch ./out-www/dummy.dep
: David Nalesnik
To: Julien Rioux
Cc: LilyPond Devel
Sent: Sunday, March 17, 2013 2:17 AM
Subject: Re: make doc fails
Julien,
On Sat, Mar 16, 2013 at 7:31 PM, Julien Rioux wrote:
On 16/03/2013 6:27 PM, David Nalesnik wrote:
/usr/bin/python -tt
/home/david/lilypond
Julien,
On Sat, Mar 16, 2013 at 7:31 PM, Julien Rioux wrote:
> On 16/03/2013 6:27 PM, David Nalesnik wrote:
>
>> /usr/bin/python -tt
>> /home/david/lilypond-git/**scripts/build/create-weblinks-**itexi.py >
>> out-www/weblinks.itexi
>> make[3]: *** No rule to make target
>> `/home/david/lilypond-
On 16/03/2013 6:27 PM, David Nalesnik wrote:
/usr/bin/python -tt
/home/david/lilypond-git/scripts/build/create-weblinks-itexi.py >
out-www/weblinks.itexi
make[3]: *** No rule to make target
`/home/david/lilypond-git/Documentation/cs/web/news-front.itexi', needed by
`out-www/web.texi'. Stop.
Tr
Hi all,
I'm attempting to put two snippets dealing with the measure counter up for
review, but I'm running into problems when I run make doc. Here's the tail
end of the terminal output:
make[3]: Entering directory
`/home/david/lilypond-git/build/Documentation/cs'
/usr/bin/python -tt
/home/david/
On Aug 28, 2011, at 12:58 PM, Carl Sorensen wrote:
> On 8/28/11 3:29 AM, "m...@apollinemike.com" wrote:
>
>
>>
>> As for the convert-ly rule, I was under the impression that these rules were
>> pushed on a version-to-version basis, and all syntax changes were written as
>> one rule before the
On Aug 28, 2011, at 4:58 PM, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> To: "Phil Holmes"
> Cc: ; "Devel"
> Sent: Sunday, August 28, 2011 11:25 AM
> Subject: Re: Make doc fails
>
>
>> On Sun, Aug
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: ; "Devel"
Sent: Sunday, August 28, 2011 11:25 AM
Subject: Re: Make doc fails
On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:
I think that's fixed one problem, but
On Aug 28, 2011, at 11:45 AM, Graham Percival wrote:
> On Sun, Aug 28, 2011 at 11:29:28AM +0200, m...@apollinemike.com wrote:
>>
>> Please let me know what I could do to prevent this from happening again
>
> Since you were editing documentation, I would have liked you to
> have:
> 1. touch Docum
On 8/28/11 3:29 AM, "m...@apollinemike.com" wrote:
>
> As for the convert-ly rule, I was under the impression that these rules were
> pushed on a version-to-version basis, and all syntax changes were written as
> one rule before the rolling of the next version. The last time I added one
> was
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: ; "Devel"
Sent: Sunday, August 28, 2011 11:25 AM
Subject: Re: Make doc fails
On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:
I think that's fixed one problem, but
On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:
> I think that's fixed one problem, but I can't test because another
> change appears to have created another problem:
>
> Unbound variable: ly:stem::pure-calc-stem-end-position
> command failed: /home/phil/lilypond-git/build/out/bin/lil
Am Sunday, 28. August 2011, 11:29:28 schrieb m...@apollinemike.com:
> As for the convert-ly rule, I was under the impression that these rules
> were pushed on a version-to-version basis, and all syntax changes were
> written as one rule before the rolling of the next version.
Nope. As soon as you
On Aug 28, 2011, at 11:46 AM, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> To: "Phil Holmes" ;
> Cc: "Devel"
> Sent: Sunday, August 28, 2011 3:33 AM
> Subject: Re: Make doc fails
>
>
>> On Sun, Aug
- Original Message -
From: "Graham Percival"
To: "Phil Holmes" ;
Cc: "Devel"
Sent: Sunday, August 28, 2011 3:33 AM
Subject: Re: Make doc fails
On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:
On Sat, Aug 27, 2011 at 05:14:00PM +0
On Sun, Aug 28, 2011 at 11:29:28AM +0200, m...@apollinemike.com wrote:
>
> Please let me know what I could do to prevent this from happening again
Since you were editing documentation, I would have liked you to
have:
1. touch Documentation/*.te??
(this tells make to check all manuals to see if
On Aug 28, 2011, at 4:33 AM, Graham Percival wrote:
> On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:
>> On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
>>> This afternoon I've done a fresh pull, make and make doc. Make doc
>>> failed with this:
>>
>> Indeed. It ne
On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:
> On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
> > This afternoon I've done a fresh pull, make and make doc. Make doc
> > failed with this:
>
> Indeed. It needed to run
> scripts/auxiliar/makelsr.py
> I've just do
On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
> This afternoon I've done a fresh pull, make and make doc. Make doc
> failed with this:
Indeed. It needed to run
scripts/auxiliar/makelsr.py
I've just done that, and will push once the build successfully
finishes.
I noticed a bunc
This afternoon I've done a fresh pull, make and make doc. Make doc failed
with this:
command failed: /home/phil/lilypond-git/build/out/bin/lilypond -dbackend=eps
[snip lots of options]
"/home/phil/lilypond-git/build/out/lybook-db/snippet-names-828948788.ly"
Then:
fatal error: failed files:
On Sun, Dec 12, 2010 at 12:19 AM, Patrick McCarty wrote:
> Okay, pushed.
Thanks! That was embarrassing.
Cheers,
Valentin.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2010-12-12, Valentin Villenave wrote:
> On Sat, Dec 11, 2010 at 11:17 PM, Patrick McCarty wrote:
> > The patch below seems to work. Is this the correct fix?
>
> Of course! Please push asap.
Okay, pushed.
Thanks,
Patrick
___
lilypond-devel mailing
On Sat, Dec 11, 2010 at 11:17 PM, Patrick McCarty wrote:
> The patch below seems to work. Is this the correct fix?
Of course! Please push asap.
I ran make check but it didn't occur to me that the ukulele needed to
be modified as well. Stupid me.
Cheers,
Valentin.
__
On 2010-12-11, Patrick McCarty wrote:
>
> I can't run `make doc' due to a compile failure on git master (as of
> commit 75cdeeefba1e4762a29b5f418b8d6294a0eba18e).
>
> Valentin, do you have a fix for this?
The patch below seems to work. Is this the correct fix?
diff --git a/ly/predefined-ukule
Hello,
I can't run `make doc' due to a compile failure on git master (as of
commit 75cdeeefba1e4762a29b5f418b8d6294a0eba18e).
The relevant snippet that fails is in fretted-strings.itely:
\version "2.13.42"
\include "predefined-ukulele-fretboards.ly"
myChords = \chordmode { a1 a:m a:aug }
On Thu, Dec 09, 2010 at 10:09:50AM -0700, Carl Sorensen wrote:
> I've got commit 16bdb67bb1ce1f52380b36e264869c2b61aa3553
I'm guessing that you fxied this in e7477, since git master looks
fine to me in 1ba780. I just rebuilt everything from scratch with
no problems.
Cheers,
- Graham
___
I've got commit 16bdb67bb1ce1f52380b36e264869c2b61aa3553
I did
make clean && make
make doc-clean
make doc
I get this error:
Interpreting music...
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-20.otf
]
elapsed time: 0.01 seconds
Element count 113 (spanners 11)
Preproc
Erik Sandberg wrote:
Hi,
gub seems to work fairly well now. However, there are some problems: make doc
fails on the following snippet, seems to be a GC problem. A portion of the
output is attached.
You can trouble shoot this in GDB - just set a breakpoint on abort().
Also, the patches I
Hi,
gub seems to work fairly well now. However, there are some problems: make doc
fails on the following snippet, seems to be a GC problem. A portion of the
output is attached.
Also, the patches I applied yesterday (updating \midi {\tempo}) are needed to
finish make doc, but the autotester
42 matches
Mail list logo
