On 2024-11-30 13:37, Jean-Charles Malahieude wrote:
On a fresh repo, make doc chokes on
input/regression/include-path-modification and I'm unable to resolve this.
Excerpt of the log:
```
Renaming input to: `include-path-modification-i.ly'
include-path-modification-i.ly:13:2: error: Guile signa
Hi,
On a fresh repo, make doc chokes on
input/regression/include-path-modification and I'm unable to resolve this.
The log file is attached.
Cheers,
--
Jean-CharlesGNU LilyPond 2.25.22 (running Guile 3.0)
Processing `12/lily-b0020de6.ly'
Parsing...
Renaming input to: `include-path-modificatio
On 29/11/2011 6:15 PM, Graham Percival wrote:
On Tue, Nov 29, 2011 at 05:28:37PM -0500, Julien Rioux wrote:
This is a sequential make and make doc. The latter stops with the
error message given below. Extract_texi_filename is the last thing
that runs correctly and then make tries to copy a file
On 29/11/2011 6:24 PM, James wrote:
Julien
On 29 November 2011 22:28, Julien Rioux wrote:
Hi all,
In a fresh checkout I run
./autogen.sh --noconfigure
mkdir build0
cd build0
../configure --disable-optimising
make&& make doc
This is a sequential make and make doc. The latter stops with the
On Tue, Nov 29, 2011 at 05:28:37PM -0500, Julien Rioux wrote:
> This is a sequential make and make doc. The latter stops with the
> error message given below. Extract_texi_filename is the last thing
> that runs correctly and then make tries to copy a file from the
> build dir instead of the source
Julien
On 29 November 2011 22:28, Julien Rioux wrote:
> Hi all,
>
> In a fresh checkout I run
> ./autogen.sh --noconfigure
> mkdir build0
> cd build0
> ../configure --disable-optimising
> make && make doc
>
> This is a sequential make and make doc. The latter stops with the error
> message given
this is the first time I experience
this make doc failure.
Just looking for some confirmation so that I can identify if I did
something wrong or not.
Thanks,
Julien
/home/jrioux/git/lilypond/build0/scripts/build/out/extract_texi_filenames -o
/home/jrioux/git/lilypond/build0/./out-www/xref
Hello,
On Tue, Nov 8, 2011 at 1:35 AM, Colin Campbell wrote:
> On 11-11-07 12:46 PM, Adam Spiers wrote:
>>
>> On Mon, Nov 7, 2011 at 7:34 PM, Neil Puttock wrote:
>>>
>>> On 7 November 2011 19:32, Graham Percival
>>> wrote:
>>>
Failing either of these, I guess we're into git bisect time, wh
On 11-11-07 12:46 PM, Adam Spiers wrote:
On Mon, Nov 7, 2011 at 7:34 PM, Neil Puttock wrote:
On 7 November 2011 19:32, Graham Percival wrote:
Failing either of these, I guess we're into git bisect time, which
of course sucks for doc-building if you're not Phil or James. I
know that Phil can
On Mon, Nov 7, 2011 at 7:34 PM, Neil Puttock wrote:
> On 7 November 2011 19:32, Graham Percival wrote:
>
>> Failing either of these, I guess we're into git bisect time, which
>> of course sucks for doc-building if you're not Phil or James. I
>> know that Phil can build the docs, but hopefully Ja
On 7 November 2011 19:32, Graham Percival wrote:
> Failing either of these, I guess we're into git bisect time, which
> of course sucks for doc-building if you're not Phil or James. I
> know that Phil can build the docs, but hopefully James' computer
> will fail in this same way?
I've just fini
On Mon, Nov 07, 2011 at 05:00:23PM +, Adam Spiers wrote:
> extract_texi_filenames.py: Processing out-www/snippets.texi
> Traceback (most recent call last):
> File
> "/home/adam/.GIT/3rd-party/lilypond/build/scripts/build/out/extract_texi_filenames",
> line 304, in
> Traceback (most recent c
- Original Message -
From: "Peekay Ex"
To: "Phil Holmes" ; "Adam Spiers"
Cc:
Sent: Monday, November 07, 2011 5:26 PM
Subject: Re: make doc failure on fresh build tree
Hello,
On Mon, Nov 7, 2011 at 5:14 PM, Phil Holmes wrote:
- Original Message
Hello,
On Mon, Nov 7, 2011 at 5:14 PM, Phil Holmes wrote:
> - Original Message - From: "Adam Spiers"
>
> To:
> Sent: Monday, November 07, 2011 5:00 PM
> Subject: make doc failure on fresh build tree
>
>
>> The below error was caused by 'ma
- Original Message -
From: "Adam Spiers"
To:
Sent: Monday, November 07, 2011 5:00 PM
Subject: make doc failure on fresh build tree
The below error was caused by 'make -j2 doc' on a fresh build tree -
any ideas?
/home/adam/.GIT/3rd-party/lilypond/bui
The below error was caused by 'make -j2 doc' on a fresh build tree -
any ideas?
/home/adam/.GIT/3rd-party/lilypond/build/scripts/build/out/extract_texi_filenames
-I ./out-www -I /home/adam/music/software/lilypond.git/Documentation
-I /home/adam/music/software/lilypond.git/Documentation -o
/home/ad
On Fri, Nov 13, 2009 at 09:36:44PM +, Neil Puttock wrote:
> > I guess I could test this tomorrow.
>
> Doesn't work for me unfortunately:
>
> WARNING: Unable to find node 'Scheme tutorial' in book learning.
> cp /home/neil/lilypond/Documentation/css/*.css out-www/contributor/
> cp /home/neil/l
2009/11/13 Graham Percival :
> I guess I could test this tomorrow.
Doesn't work for me unfortunately:
WARNING: Unable to find node 'Scheme tutorial' in book learning.
cp /home/neil/lilypond/Documentation/css/*.css out-www/contributor/
cp /home/neil/lilypond/Documentation/css/*.css out-www/notati
On Fri, Nov 13, 2009 at 10:08:36PM +0100, Matthias Kilian wrote:
> On Fri, Nov 13, 2009 at 08:31:34PM +, Carl Sorensen wrote:
> > @@ -146,8 +146,8 @@ local-WWW-1: $(OUT_TEXINFO_MANUALS)
> > $(PDF_FILES) info
> >
> > local-WWW-2: txt-to-html $(OUT_HTML_FILES) $(DEEP_HTML_FILES)
> > $(source
On Fri, Nov 13, 2009 at 08:31:34PM +, Carl Sorensen wrote:
> @@ -146,8 +146,8 @@ local-WWW-1: $(OUT_TEXINFO_MANUALS)
> $(PDF_FILES) info
>
> local-WWW-2: txt-to-html $(OUT_HTML_FILES) $(DEEP_HTML_FILES)
> $(source-links) $(OM
> # fix links from other manuals to general
> - fi
raham Percival percival-music.ca> writes:
>
> On Thu, Oct 22, 2009 at 07:34:18AM -0600, Carl Sorensen wrote:
> > # fix links from other manuals to general
> > find ./out-www -name "*.html" |
xargs sed -i 's/\.\.\/general\//\.\.\//'
> > sed: 1: "./out-www/All.html": invalid command code .
>
> M
On Thu, Oct 22, 2009 at 07:34:18AM -0600, Carl Sorensen wrote:
> # fix links from other manuals to general
> find ./out-www -name "*.html" | xargs sed -i 's/\.\.\/general\//\.\.\//'
> sed: 1: "./out-www/All.html": invalid command code .
Mao. IIRC you're on OSX? Evidently this is a difference bet
With current git, after make, make doc-clean, make doc I get
WARNING: Unable to find node 'Scheme tutorial' in book learning.
cp /Users/Carl/lilypond-working/Documentation/css/*.css out-www/contributor/
# fix links from other manuals to general
find ./out-www -name "*.html" | xargs sed -i 's/\.\.\
On 2009-10-17, Graham Percival wrote:
> On Sat, Oct 17, 2009 at 04:39:01PM +0200, Jean-Charles Malahieude wrote:
> > Here is the tail of the logs when trying to build the
> > documentation on a fresh master with the last CVS of texi2html:
>
> Hmm... don't use texi2html CVS? :)
Yeah, texi2html C
On Sat, Oct 17, 2009 at 04:39:01PM +0200, Jean-Charles Malahieude wrote:
> Here is the tail of the logs when trying to build the documentation on a
> fresh master with the last CVS of texi2html:
Hmm... don't use texi2html CVS? :)
> Undefined subroutine &main:: called at
> /home/jcharles/GIT/
Hi everybody!
Here is the tail of the logs when trying to build the documentation on a
fresh master with the last CVS of texi2html:
==
home/jcharles/GIT/Mentors/./out-www/xref-maps out-www/collated-files.texi
ln -f /home/jcharles/GIT/Mentors/Documentation/css/lilypond-b
2009/8/11 John Mandereau :
> Getting the Y-offset of InstrumentName seems to be really needed in this
> particular snippet; I'll probably push the dirty fix below to be able to
> complete the docs build (plus a FIXME in the texidoc) until this snippet
> is really fixed.
Sorry for the delay, John;
Le mardi 11 août 2009 à 15:44 +0200, John Mandereau a écrit :
> It looks like a grob suicides in Documentation/snippets/incipit.ly, as I
> get the backtrace below when issuing 'make doc'. I suspect a check for
> SCM_UNSPECIFIED should be added either in the override in incipit.ly or
> in system-st
Hi Neil,
It looks like a grob suicides in Documentation/snippets/incipit.ly, as I
get the backtrace below when issuing 'make doc'. I suspect a check for
SCM_UNSPECIFIED should be added either in the override in incipit.ly or
in system-start-text::calc-y-offset definition, unless there should be
n
29 matches
Mail list logo
