Am Samstag, dem 20.02.2021 um 17:04 +0200 schrieb Dave Plater:
> Hi, I'm getting a build failure:
> home/abuild/rpmbuild/BUILD/lilypond-2.22.0/mf # make
> Making mf/out/feta11.pfb < mf
> mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
> another
> Hi, I'm getting a build failure:
> home/abuild/rpmbuild/BUILD/lilypond-2.22.0/mf # make
> Making mf/out/feta11.pfb < mf
> mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
> another way to convert feta11.pt1 to feta11.pfb
You seem t
Hi, I'm getting a build failure:
home/abuild/rpmbuild/BUILD/lilypond-2.22.0/mf # make
Making mf/out/feta11.pfb < mf
mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
another way to convert feta11.pt1 to feta11.pfb
make: *** [GNUmakefile:37: out/feta11.log] Er
LGTM
https://codereview.appspot.com/320360043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2017/03/08 17:36:40, pkx166h wrote:
My error message is similar it is this:
Thank you for showing your error message.
It looks the same as mine.
I've created a patch for fixing `make check` error only.
Would you try it?
https://sourceforge.net/p/testlilyissues/issues/5077/#28bc
This patch
On 2017/03/08 11:43:26, trueroad wrote:
On 2017/03/04 18:03:37, pkx166h wrote:
> I am going to need some help from a developer on this as not being a
programmer
> I don't know what that last comment means I need to do on my side.
I've tried Patch Set 1.
I could not reproduce errors.
Would you
Benkő Pál writes:
> 2017-03-04 19:03 GMT+01:00 :
>> On 2017/02/25 15:19:47, felix.janda_posteo.de wrote:
>>>
>>> The fix probably breaks compilation on everything not using glibc:
>
> Is lilypond supposed to be built on anything outside GNU/Linux?
More or less yes. Heeding reports and warnings
2017-03-04 19:03 GMT+01:00 :
> On 2017/02/25 15:19:47, felix.janda_posteo.de wrote:
>>
>> The fix probably breaks compilation on everything not using glibc:
Is lilypond supposed to be built on anything outside GNU/Linux?
___
lilypond-devel mailing list
On 2017/03/04 18:03:37, pkx166h wrote:
I am going to need some help from a developer on this as not being a
programmer
I don't know what that last comment means I need to do on my side.
I've tried Patch Set 1.
I could not reproduce errors.
Would you show me your environment and detailed repro
On 2017/02/25 15:19:47, felix.janda_posteo.de wrote:
The fix probably breaks compilation on everything not using glibc:
get_current_dir_name() is glibc specific, and not available on other
systems, so its invocation should be protected with an #ifdef
__GLIBC__
or via an autoconf test.
As
The fix probably breaks compilation on everything not using glibc:
get_current_dir_name() is glibc specific, and not available on other
systems, so its invocation should be protected with an #ifdef __GLIBC__
or via an autoconf test.
As indicated in the man page, even on glibc, to use this functio
e for target 'test'
failed
make: ** [test] Error 2
--snip--
Is this something that is bound to happen and cannot be tested normally
or is this something that the patch submitter didn't take into account
on our side or something else such as a specific configuration
environment th
- Original Message -
From: "Graham Percival"
To: "Francisco Vila"
Cc: "Phil Holmes" ;
Sent: Tuesday, June 05, 2012 4:19 PM
Subject: Re: another GUB build failure from translations
On Tue, Jun 05, 2012 at 05:15:54PM +0200, Francisco Vila wrote:
201
On Tue, Jun 05, 2012 at 05:15:54PM +0200, Francisco Vila wrote:
> 2012/6/5 Phil Holmes :
> > It looks like an error in the French translation's file name - it's there as
> > broken-crescendo-hairpin.ly whereas in es/texidocs/ (for example) it's
> > broken-crescendo-hairpin.texidoc
>
> Ah yes, than
2012/6/5 Phil Holmes :
> It looks like an error in the French translation's file name - it's there as
> broken-crescendo-hairpin.ly whereas in es/texidocs/ (for example) it's
> broken-crescendo-hairpin.texidoc
Ah yes, thank you, I will fix it in staging. Right?
--
Francisco Vila. Badajoz (Spain)
- Original Message -
From: "Francisco Vila"
To: "Graham Percival"
Cc:
Sent: Tuesday, June 05, 2012 3:52 PM
Subject: Re: another GUB build failure from translations
2012/6/5 Graham Percival :
file from VC not distributed:
lilypond-2.15.40/Documentation/fr/texid
2012/6/5 Graham Percival :
> file from VC not distributed:
> lilypond-2.15.40/Documentation/fr/texidocs/broken-crescendo-hairpin.ly
How is this possible?
Documentation/xx/texicods/GNUmakefile is identical for xx = es fr de etc.
In case this is not only possible but a fact, how could we have avoi
file from VC not distributed:
lilypond-2.15.40/Documentation/fr/texidocs/broken-crescendo-hairpin.ly
rm -rf /tmp/tmpEc298t
Traceback (most recent call last):
File "test-lily/dist-check.py", line 137, in
main ()
File "test-lily/dist-check.py", line 132, in main
check_files (tarball, rep
On 09/24/2011 12:37 AM, Reinhold Kainhofer wrote:
The problem with guile 2.0 is that it includes many major changes (compiled
code, new macro handling, new garbage collection, completely new
string/unicode handling, etc.), which also require major code changes and
restructuring. Lilypond, however
Am Friday, 23. September 2011, 23:00:45 schrieb Dave Plater:
> If lilypond is unable to use guile 2.0 it's the only
> hope although my personal opinion is the easiest route is fixing the
> compilation problem. A failed documentation build I can work around by
> using the doc tarball a failed progra
On 09/23/2011 05:37 PM, Ian Hulin wrote:
Hi Dave,
Lilypond (V2.14) needs to have Guile V1.8.7 minimum and V1.8.8 maximum
to work. We are currently working on migrating to use Guile V2.0 but
it's slow progress owing to the close-knit integration between Lily
and Guile. The migration work will n
Out of curiosity: guile2 will make rendering faster for lilypond?
Other advantages?
Since compilation time of big scores annoys lots of people, that would
be good to have.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mail
Hi Dave,
Lilypond (V2.14) needs to have Guile V1.8.7 minimum and V1.8.8 maximum
to work. We are currently working on migrating to use Guile V2.0 but
it's slow progress owing to the close-knit integration between Lily
and Guile. The migration work will not be available in time for
V2.16, either.
On 09/23/2011 02:15 PM, Peekay Ex wrote:
Dave,
On Fri, Sep 23, 2011 at 12:54 PM, Dave Plater wrote:
On 09/23/2011 01:40 PM, Dave Plater wrote:
I am the sole maintainer and packager of openSUSE lilypond and I have a
build failure in factory builds that appears to be guile related
On 09/23/2011 02:03 PM, David Kastrup wrote:
Dave Plater writes:
On 09/23/2011 01:40 PM, Dave Plater wrote:
I am the sole maintainer and packager of openSUSE lilypond and I
have a build failure in factory builds that appears to be guile
related,
unfortunately guile is new to me and I&#
Dave,
On Fri, Sep 23, 2011 at 12:54 PM, Dave Plater wrote:
> On 09/23/2011 01:40 PM, Dave Plater wrote:
>>
>> I am the sole maintainer and packager of openSUSE lilypond and I have a
>> build failure in factory builds that appears to be guile related,
>> unfortunately
Dave Plater writes:
> On 09/23/2011 01:40 PM, Dave Plater wrote:
>> I am the sole maintainer and packager of openSUSE lilypond and I
>> have a build failure in factory builds that appears to be guile
>> related,
>> unfortunately guile is new to me and I'm battling
I am the sole maintainer and packager of openSUSE lilypond and I have a build failure in factory builds that appears to be guile related,
unfortunately guile is new to me and I'm battling to get all the packages used by lilypond synced up and built for 11.4 in
home:plater:lilypond. I'v
Am Montag, 15. August 2011, 23:51:51 schrieb Graham Percival:
> I also
> ignored GUB master not working on my machine in favor of using the
> older stable-2.14 branch to compile all the 2.15 releases. But
> since we've hit this snag, we might as well start afresh by trying
> to make GUB master wor
Neil Puttock schreef op vr 04-03-2011 om 23:08 [+]:
> There were two bugs: missing snippets from the harmonics patch and an
> undocumented translation property (restCompletionBusy).
>
> Both fixed in master.
Thanks!
Jan
--
Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
Freelance IT h
On 4 March 2011 22:56, m...@apollinemike.com wrote:
> I think that the commit with SHA1 ID b02ea152073d11899bb17eecabe4d47a6009756d
> may have caused this:
>
> Writing "internals.texi"...ERROR: In procedure procedure-name:
> ERROR: Wrong type argument in position 1: #f
>
> I'm not sure, though, a
I think that the commit with SHA1 ID b02ea152073d11899bb17eecabe4d47a6009756d
may have caused this:
Writing "internals.texi"...ERROR: In procedure procedure-name:
ERROR: Wrong type argument in position 1: #f
I'm not sure, though, and don't have time to do a git bisect now. Can anyone
confirm t
Mike Solomon schreef op di 01-03-2011 om 08:10 [-0500]:
> Pushed.
Thanks for making this quick fix. I changed it to use my_round
for sake of consistency. I would appreciate a bit clearer
commit message, I would have written something like
Avoid using std::round (). Fixes build on freebsd.
Graham Percival schreef op di 01-03-2011 om 13:05 [+]:
> On 2/28/11, Graham Percival wrote:
> > On 2/28/11, Jan Nieuwenhuizen wrote:
> Could somebody comment out this stuff so that we can have a release?
> Or just add 0.5 and cast to an int? I don't care whether floats are
> "impure" or wha
On Mar 1, 2011, at 8:05 AM, Graham Percival wrote:
> On 2/28/11, Graham Percival wrote:
>> On 2/28/11, Jan Nieuwenhuizen wrote:
>>> Graham Percival schreef op ma 28-02-2011 om 09:35 [+]:
/main/src/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/bea
On 2/28/11, Graham Percival wrote:
> On 2/28/11, Jan Nieuwenhuizen wrote:
>> Graham Percival schreef op ma 28-02-2011 om 09:35 [+]:
>>> /main/src/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/beam-quanting.cc:638:
>>> error: 'round' was not declared in
On 2/28/11, Jan Nieuwenhuizen wrote:
> Graham Percival schreef op ma 28-02-2011 om 09:35 [+]:
>> /main/src/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/beam-quanting.cc:638:
>> error: 'round' was not declared in this scope
>>
>> I'm guessing that you n
Graham Percival schreef op ma 28-02-2011 om 09:35 [+]:
> /main/src/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/beam-quanting.cc:638:
> error: 'round' was not declared in this scope
>
> I'm guessing that you need to explicitly include some other header
/main/src/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/beam-quanting.cc:638:
error: 'round' was not declared in this scope
I'm guessing that you need to explicitly include some other header
because round() is in default in glibc but not in freebsd libc, or
On 1/8/11 5:41 PM, "Mike Solomon" wrote:
> Following Carl's advice, I ran a make-check and got the following issue:
>
> command failed: /Users/mikesolomon/devel/lilypond/out/bin/lilypond -I ./ -I
> ./out-test -I ../../input -I /Users/mikesolomon/devel/lilypond/Documentation
> -I /Users/mikesolom
Following Carl's advice, I ran a make-check and got the following issue:
command failed: /Users/mikesolomon/devel/lilypond/out/bin/lilypond -I ./ -I
./out-test -I ../../input -I /Users/mikesolomon/devel/lilypond/Documentation -I
/Users/mikesolomon/devel/lilypond/Documentation/snippets -I
../../
On 12/10/2010 05:13 PM, Patrick McCarty wrote:
> On Fri, Dec 10, 2010 at 6:40 AM, Graham Percival
> wrote:
>
>> On Fri, Dec 10, 2010 at 04:19:59PM +0200, Dave Plater wrote:
>>
>>> I'll try the texlive-bin maintainer. Is this going to be a problem with
>>> 2.13.42 do you think?
>>>
>
On Fri, Dec 10, 2010 at 6:40 AM, Graham Percival
wrote:
> On Fri, Dec 10, 2010 at 04:19:59PM +0200, Dave Plater wrote:
>> I'll try the texlive-bin maintainer. Is this going to be a problem with
>> 2.13.42 do you think?
>
> I expect it would still be a problem. Or rather, if 2.13.42 works
> when 2
On Fri, Dec 10, 2010 at 04:19:59PM +0200, Dave Plater wrote:
> I'll try the texlive-bin maintainer. Is this going to be a problem with
> 2.13.42 do you think?
I expect it would still be a problem. Or rather, if 2.13.42 works
when 2.12.3 doesn't, then it would be an accident rather than on
purpose
On 12/10/2010 03:48 PM, Graham Percival wrote:
> On Fri, Dec 10, 2010 at 03:16:27PM +0200, Dave Plater wrote:
>
>> On 12/10/2010 03:00 PM, Graham Percival wrote:
>>
>>> Huh. Be aware that bib2html is no longer in git; we now use
>>> bib2texi. I expect that it would have the same problem,
On Fri, Dec 10, 2010 at 03:16:27PM +0200, Dave Plater wrote:
> On 12/10/2010 03:00 PM, Graham Percival wrote:
> > Huh. Be aware that bib2html is no longer in git; we now use
> > bib2texi. I expect that it would have the same problem, though.
> >
> I'm about to start packaging 2.13.42 for openSUSE
On 12/10/2010 03:00 PM, Graham Percival wrote:
> On Fri, Dec 10, 2010 at 01:52:11PM +0100, David Kastrup wrote:
>
>> Dave Plater writes:
>>
>>> bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p).
>>> I couldn't open file name `/tmp/tmp65e8GYbib2html.blg'
>>>
>>> And the sa
On Fri, Dec 10, 2010 at 01:52:11PM +0100, David Kastrup wrote:
> Dave Plater writes:
> > bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p).
> > I couldn't open file name `/tmp/tmp65e8GYbib2html.blg'
> >
> > And the same result. Can you spot any change in the normal bibtex behavio
Dave Plater writes:
>>
> I did that and it gives the same error, I made a local build and entered
> the directory :
> Arbuthnot:/usr/src/packages # pushd
> /usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography
> /usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography
> /
On 12/10/2010 01:53 PM, Graham Percival wrote:
> On Fri, Dec 10, 2010 at 01:03:37PM +0200, Dave Plater wrote:
>
>> Hi, openSUSE:Factory lilypond is failing to build documentation since
>> texlive was updated, I've added the updated texlive-bin package to the
>> successful 11.3 build and it cause
On Fri, Dec 10, 2010 at 01:03:37PM +0200, Dave Plater wrote:
> Hi, openSUSE:Factory lilypond is failing to build documentation since
> texlive was updated, I've added the updated texlive-bin package to the
> successful 11.3 build and it causes the same failure.
> I can't quite understand bibtex's u
Hi, openSUSE:Factory lilypond is failing to build documentation since
texlive was updated, I've added the updated texlive-bin package to the
successful 11.3 build and it causes the same failure.
I can't quite understand bibtex's use of /tmp in this failure :
make[3]: Entering directory
`/usr/src/pa
On 12/28/09 2:31 PM, "John Mandereau" wrote:
> Le lundi 28 décembre 2009 à 21:18 +, Graham Percival a écrit :
>> I found the same problem with a fresh build, but then I remembered
>> that I'd switched back to 2.12.2 to build new regtests for the
>> comparison to 2.12.3. When I switched ba
2009/12/28 John Mandereau :
>
> Did git issue some warnings about left files when switching back to
> 2.13?
I don't know; this was a few days ago.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/lis
Le lundi 28 décembre 2009 à 21:18 +, Graham Percival a écrit :
> I found the same problem with a fresh build, but then I remembered
> that I'd switched back to 2.12.2 to build new regtests for the
> comparison to 2.12.3. When I switched back to master after that, git
> left some old files in
2009/12/28 John Mandereau :
> Le lundi 28 décembre 2009 à 19:35 +, Graham Percival a écrit :
>> 2009/12/27 John Mandereau :
>> In git version
>> 17c304bf59498a0c19fbc215383a2ff333c7c184 I have the same problem:
>> cp -p web.texi out-www/web.texi
>
> Again, I don't know where this command come
Le lundi 28 décembre 2009 à 19:35 +, Graham Percival a écrit :
> 2009/12/27 John Mandereau :
> > Le dimanche 27 décembre 2009 à 14:34 +0100, John Mandereau a écrit :
> >> Ugh, this touch is unnecessary.
> >
> > I see, it was added because some translated Texinfo documents missed a
> > @document
2009/12/27 John Mandereau :
> Le dimanche 27 décembre 2009 à 14:34 +0100, John Mandereau a écrit :
>> Le dimanche 27 décembre 2009 à 01:02 +, Graham Percival a écrit :
>> > writing: /main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
>> > touch -r out-www/usage.texi
>> > /main/src/bu
Le dimanche 27 décembre 2009 à 14:34 +0100, John Mandereau a écrit :
> Le dimanche 27 décembre 2009 à 01:02 +, Graham Percival a écrit :
> > writing: /main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
> > touch -r out-www/usage.texi
> > /main/src/build-lilypond/./out-www/xref-maps/u
Le dimanche 27 décembre 2009 à 14:34 +0100, John Mandereau a écrit :
> Even in a build , the command should be
> cp -p ./web.texi out-www/web.texi
I meant "Even in a build from the source tree...".
Sorry,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
__
Le dimanche 27 décembre 2009 à 01:02 +, Graham Percival a écrit :
> writing: /main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
> touch -r out-www/usage.texi
> /main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
Ugh, this touch is unnecessary.
> cp -p web.texi out-www/
writing: /main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
touch -r out-www/usage.texi
/main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
cp -p web.texi out-www/web.texi
cp: cannot stat `web.texi': No such file or directory
make[3]: *** [out-www/web.texi] Error 1
make[3]: L
Tried it, compiles fine for me on Linux (the Lilybuntu virtual machine).
Thanks!
thSoft
On 2009.12.21., at 12:42, Nicolas Sceaux wrote:
> I've commited a fix. I hope it does not break things on other platforms...
> If it does, please revert patch 6b78efc2ea0cb064850c264ff225d9930353a178.
>
> Huh
Le 15 déc. 2009 à 07:20, Patrick McCarty a écrit :
> On 2009-12-14, Harmath Dénes wrote:
>> On 2009.12.13., at 20:31, Patrick McCarty wrote:
>>
>>> 2009/12/12 Harmath Dénes :
And yes, this solved the problem! You're right, flex is among the
dependencies.
Concluding it, I think two
On 2009-12-14, Harmath Dénes wrote:
> On 2009.12.13., at 20:31, Patrick McCarty wrote:
>
> > 2009/12/12 Harmath Dénes :
> >> And yes, this solved the problem! You're right, flex is among the
> >> dependencies.
> >> Concluding it, I think two things may be worth adding to the CG
> >> 2.1.6: * the w
On 2009.12.13., at 20:31, Patrick McCarty wrote:
> 2009/12/12 Harmath Dénes :
>> And yes, this solved the problem! You're right, flex is among the
>> dependencies.
>> Concluding it, I think two things may be worth adding to the CG 2.1.6:
>> * the workaround of the C++ related problem: perl -pi -e
2009/12/12 Harmath Dénes :
> And yes, this solved the problem! You're right, flex is among the
> dependencies.
> Concluding it, I think two things may be worth adding to the CG 2.1.6:
> * the workaround of the C++ related problem: perl -pi -e
> 's|__vector|lily_vector|g' flower/include/std-vector
And yes, this solved the problem! You're right, flex is among the dependencies.
Concluding it, I think two things may be worth adding to the CG 2.1.6:
* the workaround of the C++ related problem: perl -pi -e
's|__vector|lily_vector|g' flower/include/std-vector.hh
* in case someone isn't familiar w
On 12/12/09 9:07 AM, "Harmath Dénes" wrote:
> On 2009.12.11., at 16:34, Carl Sorensen wrote:
>
>> Have you set the flelexer file in config.make to opt/local instead of
>> use?
>>
>> Carl Sorensen
>
> Strangely, I have no /opt/local/include/FlexLexer.h, but I indeed have
> /usr/include/FlexL
Begin forwarded message:
On 2009.12.11., at 16:34, Carl Sorensen wrote:
> Have you set the flelexer file in config.make to opt/local instead of
> use?
>
> Carl Sorensen
Strangely, I have no /opt/local/include/FlexLexer.h, but I indeed have
/usr/include/FlexLexer.h
Setting FLEXLEXER_FILE = /o
> Have you tried the suggested fix from the second thread?
>
> Something like
>
> sed -i 's|__vector|lily_vector|g' flower/include/std-vector.hh
>
> might be worth a try.
>
> Regards,
> Neil
You are right, according to
http://www.mail-archive.com/fink-us...@lists.sourceforge.net/msg29281.htm
2009/12/9 Harmath Dénes :
> Apparently, this got discussed in:
>
> http://www.mail-archive.com/fink-us...@lists.sourceforge.net/msg28916.html
> http://www.mail-archive.com/fink-us...@lists.sourceforge.net/msg29280.html
>
> but without solution. Can this be filed as a bug? Is there a workaround?
H
Oh yeah, maybe you meant Xcode. Yes, I use the standard Snow Leopard Xcode,
v3.2.1.
thSoft
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I'm using:
OS X 10.6.2
MacPorts 1.8.1
gcc 4.2.1
XQuartz 2.3.4 (Xtools? That's an abandoned project, isn't it? I think you meant
XQuartz.)
I installed all dependencies with MacPorts.
thSoft
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://
Are you using fink? Are you using the standard 10.6 xtools? What
version of gcc do they use?
Cheers,
- Graham
On Wed, Dec 09, 2009 at 04:57:05PM +0100, Harmath Dénes wrote:
> Hi all,
>
> As another attempt on building LilyPond on OS X 10.6, I managed to run
> ./autogen.sh without any errors o
Hi all,
As another attempt on building LilyPond on OS X 10.6, I managed to run
./autogen.sh without any errors or warnings. But when running make all, I get
the following C++ compilation error:
In file included from /usr/include/c++/4.2.1/vector:70,
from ./include/std-vector.hh
Op dinsdag 10-11-2009 om 23:38 uur [tijdzone +0100], schreef Harmath
Dénes:
> checking GUILE rational bugfix... ok
>From this message, it seems that the right Guile installation is
found.
However, as these earlier messages show,
> checking for scm_boot_guile in -lguile... no
> checking for scm_
Today, I updated to OS X 10.6.2 and wanted to see if it can build LilyPond or
the docs. Unfortunately, already when running autogen.sh, I got the following
error:
ERROR: Please install required programs: libguile (libguile-dev, guile-devel
or guile-dev package).
The relevant output lines are:
On 2009.11.09., at 17:16, Graham Percival wrote:
Oh, I see now. It's in Documentation/snippets/
Thanks for the info.
well, I'm at a loss as to why it can't compile. I guess you could
report it on bug-lilypond, and hopefully somebody who has OSX can
test it as well.
Reported!
In the mean
On Mon, Nov 09, 2009 at 04:28:24PM +0100, Harmath Dénes wrote:
> On 2009.11.09., at 15:49, Graham Percival wrote:
>> Not unless you have a minimal example. I also hope that you
>> noticed my warnings about COMMENTING OUT THE STUFF ABOVE THE "CUT
>> AND PASTE" SECTION.
>
> Of course. Though only th
On 2009.11.09., at 15:49, Graham Percival wrote:
Not unless you have a minimal example. I also hope that you
noticed my warnings about COMMENTING OUT THE STUFF ABOVE THE "CUT
AND PASTE" SECTION.
Of course. Though only the line
\include "lilypond-book-preamble.ly"
had to be commented out.
I
On Mon, Nov 09, 2009 at 02:42:24PM +0100, Harmath Dénes wrote:
> On 2009.11.05., at 23:02, Graham Percival wrote:
>> Take a look at TOPDIR/out/lybook-db/aa/lily-0a4411fa.ly. What's
>> in the file? Does the version number say "2.13.7" ?
>>
>> What happens if you copy the file to a new location, CO
On 2009.11.05., at 23:02, Graham Percival wrote:
Take a look at TOPDIR/out/lybook-db/aa/lily-0a4411fa.ly. What's
in the file? Does the version number say "2.13.7" ?
What happens if you copy the file to a new location, COMMENT OUT
THE STUFF ABOVE "start cut&paste section", and run lilypond on i
Please keep emails on the mailist.
On Fri, Nov 06, 2009 at 12:22:57AM +0100, Harmath Dénes wrote:
> On 2009.11.05., at 23:02, Graham Percival wrote:
>> That all looks typical. IIRC in gub we use freetype 2.3.11, but
>> that was to workaround an OSX 10.6 bug, so it shouldn't affect
>> you.
>
> Hm
On Thu, Nov 05, 2009 at 10:53:55PM +0100, Harmath Dénes wrote:
> On 2009.11.05., at 18:06, Graham Percival wrote:
>
>> BTW, are you on OSX 10.5 or 10.6?
>
> My software environment:
That all looks typical. IIRC in gub we use freetype 2.3.11, but
that was to workaround an OSX 10.6 bug, so it shoul
On 2009.11.05., at 18:06, Graham Percival wrote:
2009/11/5 Harmath Dénes :
You were right. I finally managed to put the scripts' location before
/opt/local/bin in my path, and now it proceeds. But after a while,
I get the
following error:
Pango-ERROR **: Unable to open font file /Library/Fo
Carl Sorensen schrieb:
On 10/10/09 5:59 AM, "Graham Percival" wrote:
Please don't do this. Starting from doc-clean, clean, distclean, and
./autogen, I get:
I'm sorry. I pushed a patch without testing it, because Marc has been a
reliable contributor.
Oops - sorry for the proble
2009/10/10 Carl Sorensen :
> You are correct. I had intended to get the patch set in good shape then air
> it on -devel. And then I lost track of the list it was one.
>
> I'm sorry for the mistake.
No problem, it wasn't difficult to fix.
I don't mind development discussions being split (-devel
On 10/10/09 10:29 AM, "Neil Puttock" wrote:
> 2009/10/10 Carl Sorensen :
>
>> Marc, I really need you to make sure you've tested patches before you send
>> them to me.
>
> Why are these patches posted on the tablature forum only? I think
> they deserve an airing on -devel prior to being pus
2009/10/10 Carl Sorensen :
> Marc, I really need you to make sure you've tested patches before you send
> them to me.
Why are these patches posted on the tablature forum only? I think
they deserve an airing on -devel prior to being pushed.
Regards,
Neil
___
On 10/10/09 5:59 AM, "Graham Percival" wrote:
> Please don't do this. Starting from doc-clean, clean, distclean, and
> ./autogen, I get:
I'm sorry. I pushed a patch without testing it, because Marc has been a
reliable contributor.
Marc, I really need you to make sure you've tested patches
2009/10/10 Graham Percival :
> Please don't do this. Starting from doc-clean, clean, distclean, and
> ./autogen, I get:
I've just pushed a fix.
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
Please don't do this. Starting from doc-clean, clean, distclean, and
./autogen, I get:
Processing `/main/src/lilypond/ly/generate-documentation.ly'
Parsing...
[/main/src/lilypond/ly/init.ly
[/main/src/lilypond/ly/declarations-init.ly
[/main/src/lilypond/ly/markup-init.ly]
[/main/src/lilypond
2009/8/31 Reinhold Kainhofer :
> ideally it should not be there, but I have now fixed this by setting the
> output-suffix to "1" and then clearing it. This produces the same file names
> as
> before, so that all scripts will continue working.
Cheers.
I should have mentioned there's also a copy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 31. August 2009 16:52:01 schrieb Neil Puttock:
> 2. using ly:format in make-ps-images causes scaling of PNGs to fail
> for multi-page snippets:
[...]
> Here's the line which formats the filename for each PNG:
>
> 113 (pngn (format
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 31. August 2009 18:54:10 schrieb Reinhold Kainhofer:
> Am Montag, 31. August 2009 16:52:01 schrieb Neil Puttock:
> > 1. ouput-count doesn't work,
>
> Or rather, we don't need output-count any more!
>
> > which causes the regression test
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 31. August 2009 16:52:01 schrieb Neil Puttock:
> 1. ouput-count doesn't work,
Or rather, we don't need output-count any more!
> which causes the regression test
> clip-systems.ly to fail:
>
> 82 \markup { \epsfile #X #30.0 #(format
Hi everybody,
I've just tried to do a clean build, and there are two problems
related to some recent patches:
1. ouput-count doesn't work, which causes the regression test
clip-systems.ly to fail:
82 \markup { \epsfile #X #30.0 #(format #f
"~a-1-from-2.0.1-to-4.0.1-clip.eps" (ly:parser-ou
Hi guys,
Am I the only one who sometimes hits Ghostscript failure below?
I have a x86_64 Fedora 11 box, I previously used a post-8.64 Git
snapshot of Ghostscript, which I just replaced with released version
8.70 (all self-compiled); I got this failure with post-8.64, and no
longer got it with 8.7
On Wed, Jun 10, 2009 at 8:31 PM, Andrew Hawryluk wrote:
> On Wed, Jun 10, 2009 at 5:45 AM, Jonathan Kulp
> wrote:
> > On a fresh installation of Linux Mint (and previously of xubuntu, ubuntu,
> > crunchbang, and ubuntulite) I can't get the docs to build properly. It's
> > taking several "make doc"
1 - 100 of 176 matches
Mail list logo
