Updates:
Status: Verified
Comment #9 on issue 1714 by brownian.box: Build error regarding mf2pt1 with
latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
(No comment was entered for this change
Updates:
Labels: fixed_2_14_2
Comment #7 on issue 1714 by carl.d.s...@gmail.com: Build error regarding
mf2pt1 with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
backported
___
bug-lilypond
Comment #8 on issue 1714 by carl.d.s...@gmail.com: Build error regarding
mf2pt1 with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
backported
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
> There's nothing attached, but it's in git:
> db6910b2913115769ba736e0b0ff6a159ba4
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=db6910b2913115769ba736e0b0ff6a159ba4
Thanks.
> Unfortunately it just missed the 2.15.3 release, but it will be
> included in 2.15.4.
Ok.
Updates:
Status: Fixed
Labels: fixed_2_15_4
Comment #6 on issue 1714 by percival.music.ca: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
(No comment was entered for this change
(Note: this message is in reply to an existing thread. I just subscribed
to the ML. I apologize if this creates a new thread.)
Thank you for clarifying the problem surrounding mpost.
> Attached is a fix which makes it work again in lilypond (without
> breaking backwards compatibility to older mpo
Comment #5 on issue 1714 by marc...@gmail.com: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
I built lilypond shortly after that commit and had no problems, so I think
it's
Comment #4 on issue 1714 by percival.music.ca: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
this might be fixed in
db6910b2913115769ba736e0b0ff6a159ba4
but we're leaving it unmarked for now. The
On Tue, Jun 28, 2011 at 08:14:51AM +0200, Werner LEMBERG wrote:
> Attached is a fix which makes it work again in lilypond (without
> breaking backwards compatibility to older mpost versions), and which
> I've applied to the git repository. Please test and report whether it
> works so that we can m
>> What exactly is the `latest texlive'?
>
> I may be able to test TeXLive from SVN to see if the problem
> persists.
It persists, and it is the same problem as with the Arch distribution:
mpost no longer dumps a .mem file but reads the corresponding .mp file
directly.
Attached is a fix which mak
Comment #3 on issue 1714 by marc...@gmail.com: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
I'm linking to issue 1717, since I think it may be related.
__
Comment #2 on issue 1714 by marc...@gmail.com: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
Thanks for adding this to the tracker and for looking into the problem.
The value in my texmf.cnf is
MPMEMS = .;$TEXMF
Comment #1 on issue 1714 by carl.d.s...@gmail.com: Build error regarding
mf2pt1 with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
Follow up comment from Werner Lemberg:
It seems that there are problems with the environment/configuration
> On my Arch Linux system, fully up-to-date, with the latest texlive
> in Arch's testing repo, I get the following error when trying to
> build lilypond 2.14.1 from source:
>
> "Sorry, I can't find the 'mf2pt1' preload file; will try 'plain'.This is
> MetaPost, version 1.504 (kpathsea version 6.0.1
Status: Accepted
Owner:
Labels: Type-Build Priority-Medium
New issue 1714 by brownian.box: Build error regarding mf2pt1 with latest
texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
Reported by Marc Payne,
http://lists.gnu.org/archive/html/bug-lilypond
On Mon 27 Jun 2011, 05:33 Marc Payne wrote:
> Hi there.
Hi.
Thank you, I've added this as 1714:
http://code.google.com/p/lilypond/issues/detail?id=1714
> I haven't found any references to this problem on the mailing lists or
> elsewhere, so I hope my input is useful.
>
> On my Arch Linux system
Hi there.
I haven't found any references to this problem on the mailing lists or
elsewhere, so I hope my input is useful.
On my Arch Linux system, fully up-to-date, with the latest texlive in Arch's
testing repo, I get the following error when trying to build lilypond 2.14.1
from source:
"Sorry
On Mon, Dec 14, 2009 at 9:29 PM, Pietro Cerutti wrote:
> On 2009-Dec-14, 19:46, Graham Percival wrote:
>> I've been planning on changing it (again, but for the last time)
>> to "web.tely". I'll try that tomorrow, and check the buildlog for
>> any such errors. It's possible that they only show up
On Mon, Dec 14, 2009 at 09:40:38AM +, Pietro Cerutti wrote:
> Hi, I'm the maintainer of the FreeBSD port of LilyPond.
> Since a few releases, I have a problem at the step where INFO files are
> installed. I have no experience with INFO files at all, and LilyPond's build
> system is quite comple
Hi, I'm the maintainer of the FreeBSD port of LilyPond.
Since a few releases, I have a problem at the step where INFO files are
installed. I have no experience with INFO files at all, and LilyPond's build
system is quite complex, so any insight is appreciated.
Full log here:
http://people.freebsd.
ction "Building documentation" on your install instructions page
* packages gnu-gs-fonts-std + gnu-gs-fonts-other
* kochi ttf fonts * freetype 1.3.1 + 2.1.9
* fontconfig 2.2.3 * pango 1.8.1
* guile 1.6.7
* python 2.4.2
* texinfo 4.8
* tetex 2.0.2
Steps to reproduce build error:
1
Bertalan Fodor writes:
> ln: creating symbolic link `./*.enc' to `../../../../../mf/out/*.enc':
> No such file or directory
ln fails? That's odd, unix does not fail, AFAIK. Please ask the
Cygwin folks about this.
In the mean time, just ignore this error, do make -k, or add a dash
before the co
One more:
this ln-s are done directly after configure.
Bert
I can't build lilypond, because there are no enc files:
cd /netrel/build/lilypond-2.5.26/share/lilypond/2.5.26/fonts/enc && \
ln -s ../../../../../mf/out/*.enc .
ln: creating symbolic link `./*.enc' to `../../../../../mf/out/*.enc
I can't build lilypond, because there are no enc files:
cd /netrel/build/lilypond-2.5.26/share/lilypond/2.5.26/fonts/enc && \
ln -s ../../../../../mf/out/*.enc .
ln: creating symbolic link `./*.enc' to `../../../../../mf/out/*.enc':
No such file or directory
make[1]: ***
[/netrel/build/li
[EMAIL PROTECTED] writes:
> Daniel Johnson <[EMAIL PROTECTED]> writes:
>
> > I'm getting the following error when trying to make web for Lilypond
> > 2.5.10 on a fully-up-to-date Gentoo system. It seems that lilypond is
> > choking on one of the example files. I notice that a number of other
Daniel Johnson <[EMAIL PROTECTED]> writes:
> I'm getting the following error when trying to make web for Lilypond
> 2.5.10 on a fully-up-to-date Gentoo system. It seems that lilypond is
> choking on one of the example files. I notice that a number of other
> people here are using 2.5.10, so o
I'm getting the following error when trying to make web for Lilypond
2.5.10 on a fully-up-to-date Gentoo system. It seems that lilypond is
choking on one of the example files. I notice that a number of other
people here are using 2.5.10, so obviously there's a workaround somehow.
--Daniel
===
This happens outside netrel with 2.3.6, too.
I tried to make the package. I get a Signal 11 when running the command:
cd /netrel/build/lilypond-2.3.4//Documentation/user/out &&
/netrel/build/lilyp
ond-2.3.4/lily/out/lilypond-bin --verbose
/netrel/src/lilypond-2.3.4/ly/generate
-documentation
lilypo
On Wednesday 31 March 2004 12.11, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > hi!
> >
> > I've been able to isolate the partcombine brokenness. Here's a score
> > demonstrating it:
>
> can you verify that this is fixed in CVS?
yes, it works now. thanks!
Erik
___
Bertalan Fodor writes:
> 32: ok
>
> 33: broken
Thanks. It's fixed in CVS.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
Bug-lilypond mailing l
32: ok
33: broken
34: not tried
35: broken
36: broken
Bert
> What was the last version that built correctly?
>
> Jan.
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
Fodor Bertalan writes:
> I'm trying to build 2.1.35 from the source package.
> Compile log attached.
Attachments are stripped here, could you send the log to lilypond-devel?
What was the last version that built correctly?
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The musi
I'm trying to build 2.1.35 from the source package.
I get the following error:
make[2]: *** No rule to make target
`/netrel/build/lilypond-2.1.35//python/out/lilylib.pyc', needed by
`default'. Stop.
Compile log attached.
Bert
___
Bug-lilypond mailin
I'm trying to build 2.1.35 from the source package.
I get the following error:
make[2]: *** No rule to make target
`/netrel/build/lilypond-2.1.35//python/out/lilylib.pyc', needed by
`default'. Stop.
Compile log attached.
Bert
___
Bug-lilypond mailin
34 matches
Mail list logo
