Re: Error tracking through the log files [was: Re: Compilation error with page-breaking-page-count3.ly]

Am 28.09.2012 11:38, schrieb David Kastrup: Marc Hohl writes: Well, it seems to be not as simple as that. I did a 'make test' on my patch. This fails, obviously. The console says: Dissecting... Writing snippets... Processing... Processing /home/marc/git/lilypond/out/lybook-testdb/snippet-nam

Re: Error tracking through the log files [was: Re: Compilation error with page-breaking-page-count3.ly]

Marc Hohl writes: > Well, it seems to be not as simple as that. > > I did a 'make test' on my patch. This fails, obviously. > The console says: > > Dissecting... > Writing snippets... > Processing... > Processing > /home/marc/git/lilypond/out/lybook-testdb/snippet-names-3552501373601762147.ly >

Error tracking through the log files [was: Re: Compilation error with page-breaking-page-count3.ly]

Am 28.09.2012 10:16, schrieb Marc Hohl: Am 28.09.2012 01:38, schrieb lilyp...@googlecode.com: Updates: Labels: -Patch-new Patch-needs_work Comment #33 on issue 2790 by pkx1...@gmail.com: Patch: bar-line interface part 2/2 http://code.google.com/p/lilypond/issues/detail?id=2790 Patchy say

Re: Compilation error with page-breaking-page-count3.ly

- Original Message - From: "Marc Hohl" To: Sent: Friday, September 28, 2012 9:16 AM Subject: Compilation error with page-breaking-page-count3.ly Am 28.09.2012 01:38, schrieb lilyp...@googlecode.com: Updates: Labels: -Patch-new Patch-needs_work Comment #33 on issue 27

Compilation error with page-breaking-page-count3.ly

Am 28.09.2012 01:38, schrieb lilyp...@googlecode.com: Updates: Labels: -Patch-new Patch-needs_work Comment #33 on issue 2790 by pkx1...@gmail.com: Patch: bar-line interface part 2/2 http://code.google.com/p/lilypond/issues/detail?id=2790 Patchy says 'fail on make check' - took an age to f

Re: compilation error

> > Ugh. That figures. How's HEAD? > > Still hurts. Thanks for asking. Hehe. HEAD now works :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: compilation error

Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: > Op woensdag 12-11-2008 om 10:35 uur [tijdzone +0100], schreef Werner > LEMBERG: > >> Note that `python-config --cflags' gives >> >> -I/usr/include/python2.5 \ >> -I/usr/include/python2.5 \ >> -fno-strict-aliasing \ >> -DNDEBUG \ >> -O2 \ >

Re: compilation error

Op woensdag 12-11-2008 om 10:35 uur [tijdzone +0100], schreef Werner LEMBERG: > Note that `python-config --cflags' gives > > -I/usr/include/python2.5 \ > -I/usr/include/python2.5 \ > -fno-strict-aliasing \ > -DNDEBUG \ > -O2 \ > -march=i586 \ > -mtune=i686 \ > -fmessage-length=0 \

Re: compilation error

Reinhold Kainhofer wrote: > Am Dienstag, 11. November 2008 schrieb John Mandereau: > > Yep, and the culprit was line 38 in lilylib.py, I removed it in Git. It > > was probably a leftover from before introduction of relocate-preamble in > > the Python scripts. > > Shouldn't the lines before that o

Re: compilation error

> > Your fix has a nasty side effect. Oops! It's not your fix which causes the problem, sorry. *All* tests for header files show checking XXX usability... no checking XXXpresence... no checking for XXX... no since the CPPFLAGS value isn't set correctly. From config.log: CPPFLAGS='-I/

Re: compilation error

On 2008/11/11 19:26 +0100, Reinhold Kainhofer wrote: > Shouldn't the lines before that one also be removed? They simply try to > extract a suitable value for datadir, which is not used in the file at all > any more... Yes, and it's not used in other Python libraries or scripts, but let's wait un

Re: compilation error

On 2008/11/12 00:28 +0100, Werner LEMBERG wrote: > Your fix has a nasty side effect. Running `autogen.sh' (which in turn > directly calls the configure script) gives > > ... > checking for python-config... python-config > checking Python.h usability... no > checking Python.h presence... n

Re: compilation error

> > This indeed looks like musicxml2ly is using the installed .pyc > > file instead of the newly compiled .pyc file from the local > > tree :( > > Yep, and the culprit was line 38 in lilylib.py, I removed it in Git. > It was probably a leftover from before introduction of > relocate-preamble in th

Re: compilation error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 11. November 2008 schrieb John Mandereau: > On 2008/11/11 16:25 +0100, Reinhold Kainhofer wrote: > > Am Dienstag, 11. November 2008 schrieb Werner LEMBERG: > > > I haven't done a `make uninstall' of the previous lilypond version > > > befo

Re: compilation error

On 2008/11/11 16:25 +0100, Reinhold Kainhofer wrote: > Am Dienstag, 11. November 2008 schrieb Werner LEMBERG: > > I haven't done a `make uninstall' of the previous lilypond version > > before doing a `make all' with the new version -- and, to be honest, > > this must never, ever be a prerequisite.

Re: compilation error

> I agree, but I can't reproduce this issue. What's the value of > PYTHONPATH on your system? It is not set in my environment. > Even if it includes /usr/local/share/lilypond/2.11.64/python, the > following line in make/lilypond-vars.make is supposed to prepend > python/out to PYTHONPATH: > >

Re: compilation error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 11. November 2008 schrieb Werner LEMBERG: > Another potential problem comes to my mind: Where exactly are > lilypond's python modules installed after `make install'?  Is it > possible that python uses lilypond PYC files which have been ins

Re: compilation error

On 2008/11/11 15:49 +0100, Werner LEMBERG wrote: > Another potential problem comes to my mind: Where exactly are > lilypond's python modules installed after `make install'? Is it > possible that python uses lilypond PYC files which have been installed > already, instead of using python files of th

Re: compilation error

> $ python -c 'import foo; print foo.Foo, foo.Foo(), foo.Bar, foo.Bar()' > foo.Foo > foo.Bar I get foo.Foo foo.Bar which is basically the same. This means that the problem is probably elsewhere. Attached is the output of running PYTHONVERBOSE=1 make all 2> make.all.pyth

Re: compilation error

Op maandag 10-11-2008 om 15:40 uur [tijdzone +0100], schreef Werner LEMBERG: Hi Werner, > Anything new? I can't believe that 2.5.2 compiles the current sources > just fine, while 2.5 chokes. Theoretically, this shouldn't happen -- > I coulnd't find anything on python.org which documents a synta

Re: compilation error

> > > You need to do a clean build inside python/ to make sure > > > Reinhold's musicxml2ly.py changes are compiled. > > It *was* a clean build (I always clone the repository and do `make > all; make web'). > > > I needed this change for python-2.5.2. Werner, what python-2.5 > > version are you us

Re: compilation error

> > > AttributeError: 'module' object has no attribute 'Score' > > > > > > I'm using python 2.5. Probably Jan's last change is > > > problematic? > > > > You need to do a clean build inside python/ to make sure > > Reinhold's musicxml2ly.py changes are compiled. It *was* a clean build (I always

Re: compilation error

Op donderdag 06-11-2008 om 17:07 uur [tijdzone +], schreef Neil Puttock: > 2008/11/6 Werner LEMBERG <[EMAIL PROTECTED]>: > > score = musicexp.Score () > > AttributeError: 'module' object has no attribute 'Score' > > > > I'm using python 2.5. Probably Jan's last change is problematic? >

Re: compilation error

Has anyone noticed the same problem? Werner > With current git: > > Reading MusicXML from 00a-Basics-Pitches.xml ... > Converting to LilyPond expressions... > Traceback (most recent call last): > File "../../../scripts/musicxml2ly.py", line 2518, in > main() > File ".

Re: compilation error

2008/11/6 Werner LEMBERG <[EMAIL PROTECTED]>: > > With current git: > > Reading MusicXML from 00a-Basics-Pitches.xml ... > Converting to LilyPond expressions... > Traceback (most recent call last): >File "../../../scripts/musicxml2ly.py", line 2518, in > main() >File "../../../scri

compilation error

With current git: Reading MusicXML from 00a-Basics-Pitches.xml ... Converting to LilyPond expressions... Traceback (most recent call last): File "../../../scripts/musicxml2ly.py", line 2518, in main() File "../../../scripts/musicxml2ly.py", line 2513, in main voices = c

compilation error GIT 2007-02-02 01:02

LANG= makeinfo --enable-encoding -I ./out --output=./out/lilypond-internals.info out/lilypond-internals.nexi out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'. ./out/lilypond-internals.nexi:18098: Cross reference to nonexistent node `TupletSpannerEvent' (perhaps incorr

compilation error of GIT 2007-01-26 3:56

Processing `/home/wl/git/lilypond.compiled/ly/generate-documentation.ly' [...] error: define-grob-properties.scm: cannot find interface for property: arrow Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman

compilation error with today evening's git

Processing `ly/generate-documentation.ly' Parsing...[...][out/bin/../share/lilypond/2.11.1/scm/document-backend.scm error: define-grob-properties.scm: can't find interface for property: stencils Werner ___ lilypond-devel mailing list lilypond-dev

Re: CVS 2006-Nov-11 22:30 MET compilation error

> > Or shall we start using git right now? > > I prefer this option. OK, so please tell me how to proceed. Werner PS: This is the fourth version control system I have to work with, after CVS, SVN, and hg. ___ lilypond-devel mailing list li

Re: CVS 2006-Nov-11 22:30 MET compilation error

Joe Neeman escreveu: On 11/7/06, *Han-Wen Nienhuys* <[EMAIL PROTECTED] > wrote: > Or shall we start using git right now? I prefer this option. So it is now possible to commit directly to the git repo? If so, how can we get access? Register at repo.or.cz

Re: CVS 2006-Nov-11 22:30 MET compilation error

On 11/7/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > Or shall we start using git right now?I prefer this option.So it is now possible to commit directly to the git repo? If so, how can we get access? ___ lilypond-devel mailing list lilypond-devel@gnu

Re: CVS 2006-Nov-11 22:30 MET compilation error

Werner LEMBERG escreveu: Until that time, please check http://repo.or.cz/w/lilypond.git before committing any fixes to CVS. This is tedious. Isn't it possible to execute a script after a commit operation to the git repository (similar to CVS sending an email to the commit list) which auto

Re: CVS 2006-Nov-11 22:30 MET compilation error

> Until that time, please check > >http://repo.or.cz/w/lilypond.git > > before committing any fixes to CVS. This is tedious. Isn't it possible to execute a script after a commit operation to the git repository (similar to CVS sending an email to the commit list) which automatically synchro

Re: CVS 2006-Nov-11 22:30 MET compilation error

Erlend Aasland escreveu: Fixed in CVS this was actually fixed in GIT some time ago, see http://repo.or.cz/w/lilypond.git?a=commit;h=db1423b71d013ba9ef07a74ddf15e16e6e6b4368 the plan is to move asap to GIT on savannah.gnu.org but this still is pending some technical issues (not in the last p

Re: CVS 2006-Nov-11 22:30 MET compilation error

Fixed in CVSErlendOn 11/6/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote: Processing `/home/wl/cvs/lilypond.compiled/ly/generate-documentation.ly'Parsing...[...][scm/document-backend.scmerror: define-grob-properties.scm: can't find interface for property: balloon-text Werner__

CVS 2006-Nov-11 22:30 MET compilation error

Processing `/home/wl/cvs/lilypond.compiled/ly/generate-documentation.ly' Parsing...[...][scm/document-backend.scm error: define-grob-properties.scm: can't find interface for property: balloon-text Werner ___ lilypond-devel mailing list lilypond-

Re: compilation error with CVS 2006-Nov-01 10:05 MET

> > Why do we have -Werror? > > Because we are anal retentive. Hehe :-) Even we from FreeType (who try to fix all warning messages for all compilers) don't do that. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.

Re: compilation error with CVS 2006-Nov-01 10:05 MET

Werner LEMBERG escreveu: I get this strange warning which consequently leads to an error: rm -f ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep ./out/parser.o" \ g++ -c -Woverloaded-virtual \ -DHAVE_CONFIG_H -DNDEBUG \ -I./include -I./out -I../flower/include \

compilation error with CVS 2006-Nov-01 10:05 MET

I get this strange warning which consequently leads to an error: rm -f ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep ./out/parser.o" \ g++ -c -Woverloaded-virtual \ -DHAVE_CONFIG_H -DNDEBUG \ -I./include -I./out -I../flower/include \ -I../flower/./out -I

compilation error with CVS 2006-01-27

Using gcc 3.3.3 I get this: staff-symbol-referencer.cc: In static member function `static bool Staff_symbol_referencer::on_staff_line(Grob*, int)': staff-symbol-referencer.cc:45: error: call of overloaded `fabs(int&)' is ambiguous /usr/include/bits/mathinline.h:451: error: candid

Compilation error, Was: lilypond ./ChangeLog lily/accidental-placement....

Han-Wen Nienhuys wrote: Patches: Index: lilypond/ChangeLog diff -u lilypond/ChangeLog:1.4127 lilypond/ChangeLog:1.4128 --- lilypond/ChangeLog:1.4127 Mon Sep 12 13:17:19 2005 +++ lilypond/ChangeLog Mon Sep 12 23:33:22 2005 @@ -1,3 +1,7 @@ +2005-09-13 Han-Wen Nienhuys <[EMAIL PROTECTED]> + +

Re: CVS 2004-12-29 22:58 compilation error

> > > On my system `pkg-config --cflags pangoft2' correctly returns > > > the path to the top pango header directory > > > (-I/usr/local/include/pango-1.0). A missing call to pkg-config? After further inspection I found this problematic code in configure.in: # This is developer only anyway, h

Re: CVS 2004-12-29 22:58 compilation error

> > On my system `pkg-config --cflags pangoft2' correctly returns the > > path to the top pango header directory > > (-I/usr/local/include/pango-1.0). > > > > A missing call to pkg-config? > > did you rerun autoconf and do configure once again? I *always* start with a fresh CVS, doing ./autogen.

CVS 2004-12-29 22:58 compilation error

[EMAIL PROTECTED] writes: > > I get this error: > > In file included from all-font-metrics.cc:9: > include/all-font-metrics.hh:18:25: > warning: pango/pango.h: No such file or directory > include/all-font-metrics.hh:19:28: > warning: pango/pangoft2.h: No such file or directory > >

CVS 2004-12-29 22:58 compilation error

I get this error: In file included from all-font-metrics.cc:9: include/all-font-metrics.hh:18:25: warning: pango/pango.h: No such file or directory include/all-font-metrics.hh:19:28: warning: pango/pangoft2.h: No such file or directory On my system `pkg-config --cflags pangoft2' co

Re: compilation error

On Monday March 8 2004 04:26, Mats Bengtsson wrote: > I actually find that the depencies are well documented in INSTALL.txt, > what information did you miss? > Of course, it may sometimes be tricky to find out what RPM/.dpkg > contains the necessary programs and files but that's hardly a > LilyPond

Re: compilation error

Aredridel wrote: What to do? Maybe we should just change the 'do not compile' attitude a bit, and have 'supported' development platforms with a detailed recipe to compile lily. The contributers of binary releases should make sure that the recipe stays up to date. Would this work? I'd like th

Re: compilation error

On Sat, Mar 06, 2004 at 12:44:13AM +0100, Matthias Kilian wrote: > introducing "exotic" dependencies like makeinfo CVS, there should be > also workarounds that make LilyPond (and it's documenation) compile with > standard versions (i.e. good-old makeinfo-4.5 or 4.6). Please forget what I wrote. Us

Re: compilation error

Hi! On Mon, Mar 01, 2004 at 06:36:46PM +0100, Jan Nieuwenhuizen wrote: > > Even then -- I tried to compile the texinfo CVS, which relies on a > > brand new automake version which > > Point taken; you don't need texinfo CVS. Using the current LilyPond CVS (seems to be an upcoming 2.1.29) and mak

Re: compilation error

On Tuesday March 2 2004 16:44, Jan Nieuwenhuizen wrote: > You are right. Maybe we are sending conflicting messages: do not > compile Lily! Help us (with the docs), send patches! I've still got a little bit of work ahead of me to make it so I can compile docs myself, but yet I still try to help w

Re: compilation error

> What to do? Maybe we should just change the 'do not compile' attitude > a bit, and have 'supported' development platforms with a detailed > recipe to compile lily. The contributers of binary releases should > make sure that the recipe stays up to date. Would this work? I'd like that attitude

Re: compilation error

Mats Bengtsson writes: > But, at the same time, you want to encourage people to submit > documentation patches (and other patches) and it's certainly > a big advantage if it's easy for them to build the documentation > after a change to see what it looks like before they submit the > patches. You

Re: compilation error

I'm afraid you underestimate the number of people who actually compile LilyPond themselves and have to struggle with development versions of other tools just to be able to build LilyPond. Possibly. We try our best to discourage people to do so. I see no reason whatsoever for a user to compile L

Re: compilation error

On Monday March 1 2004 10:36, Jan Nieuwenhuizen wrote: > Same goes for SVG output and a number of FOO2ly import scripts. I personally wish the scripts were better. I don't know how I would find it good to implement them though. The midi2ly didn't seem to pay much attention to what I said about

Re: compilation error

[EMAIL PROTECTED] writes: > > > Automake and autoconf deserve to wither and die, but unfortunately > > noone at GNU seems to make much of an effort to euthanasize them. > > Please explain. Do you see an alternative? Scons? (www.scons.org) -- Han-Wen Nienhuys | [EMAIL PROTECTED] |

Re: compilation error

[EMAIL PROTECTED] writes: > The biggest one is to have binary distributions that are statically linked > and can run in-place. This would help a lot of users who don't otherwise > have access to pre-built packages without requiring them to build static linking is not an option for LilyPond. GUILE

Re: compilation error

> Automake and autoconf deserve to wither and die, but unfortunately > noone at GNU seems to make much of an effort to euthanasize them. Please explain. Do you see an alternative? IMHO using autoconf has become much more reliable in the last two years or so. Werner _

Re: compilation error

Werner LEMBERG writes: > Dependencies on package versions which haven't been released yet? > Normally, relying on a CVS version is dangerous. I agree, but I don't think we ever had such dependencies (except maybe temporarily, by mistake). >> I have implemented PostScript output some three or fou

Re: compilation error

Mats Bengtsson writes: > I have to agree with others on this list. Jan and Han-Wen do a > terrific job with LilyPond. One of the few objections I have is > that they sometimes are too eager to adopt new technology. Yes, possibly. The point is that I believe in open source, and broken software ne

Re: compilation error

Mats observed: > Of course it would be nice to be able to view pictures with > examples also in the info version of the document, but I see > absolutely no reason for LilyPond to be a pioneer for this > feature. This is a very sensible observation. LilyPond is a music typesetter, hence I'm happy

Re: compilation error

[EMAIL PROTECTED] writes: > > know how to type apt-get upgrade (or suffer if they choose to use a > > more cumbersome system ;-) > > Even then -- I tried to compile the texinfo CVS, which relies on a > brand new automake version which I had to compile before, which relies > on a brand new autoconf

Re: compilation error

I have to agree with others on this list. Jan and Han-Wen do a terrific job with LilyPond. One of the few objections I have is that they sometimes are too eager to adopt new technology. Of course it would be nice to be able to view pictures with examples also in the info version of the document, bu

Re: compilation error

> > The less latest-version-or-newer packages are needed, > > the better. lilypond already needs too much packages to work. > > What package dependencies do you suggest we drop? Dependencies on package versions which haven't been released yet? Normally, relying on a CVS version is dangerous. >

Re: compilation error

Hi, Werner LEMBERG: > /home/sx0005/lilypond//Documentation/user/out/introduction.texi:68: > @image file `lily-581086212.txt' (for text) unreadable: > No such file or directory. I remember changing that to a warning some time ago. You can get rid of that message using --no-warn now. Al

Re: compilation error

> /home/sx0005/lilypond//Documentation/user/out/introduction.texi:95: > @image file `lily-212977279.txt' (for text) unreadable: As Alper says, that message is now a warning. The infinite "Too many errors" is obviously a problem, but I can't reproduce, with CVS texinfo anyway. I di

Re: compilation error

Werner LEMBERG writes: >> We could also generate dummy .txt files to satisfy makeinfo 4.6. > > Please do so. On second thought, we have do divise something smarter, because Karl wants to drop this functionality (and I think I that would be better). > The less latest-version-or-newer packages a

Re: compilation error

Karl Berry writes: > It seems to me it would be better (= less requirements of info readers) > to simply include the .txt file without the cookie in this case, as used > to be done. Yes, maybe that's better. > The best solution would be deprecate info docs without images, > > I'm not entire

Re: compilation error

> We could also generate dummy .txt files to satisfy makeinfo 4.6. Please do so. The less latest-version-or-newer packages are needed, the better. lilypond already needs too much packages to work. Werner ___ Lilypond-devel mailing list [EMAIL P

Re: compilation error

Werner LEMBERG writes: > The current compilation problem triggers a nasty bug in makeinfo 4.6: > /home/sx0005/lilypond//Documentation/user/out/introduction.texi:95: > @image file `lily-212977279.txt' (for text) unreadable: > No such file or directory. > ... > Too many errors! Gave u

compilation error

[lilypond CVS 2004-02-28 5:30 MET] The current compilation problem triggers a nasty bug in makeinfo 4.6: LANG= \ makeinfo \ -I /home/sx0005/lilypond//Documentation/user/out \ --output=/home/sx0005/lilypond//Documentation/user/out/lilypond.info \ /home/sx0005/lilypond//Documentati