Hi Bug squad,
Please be so kind to create a tracker for creating a new glyph as the LP
logo.
See discussion:
http://lilypond.1069038.n5.nabble.com/LilyPond-logo-td193408.html
Enclosed is my proposition (#10 in the former thread).
I choose this one because:
- it's the one I like most.
-
See
https://lists.gnu.org/archive/html/lilypond-user/2019-11/msg00295.html
> On 10 Dec 2019, at 22:30, B.M. van t Veer via bug-lilypond
> wrote:
>
> % Version 2.18.2 cannot run under macOS 10.15 (19A602)
> % also tried version unstable 2.19.83, same issue
>
LilyPond Internals Reference, 2.2.58 key_engraver
keyAlterationOrder(list)
It should read: "… *step *is a number from 0 to 6 and *alter *from
-2 (flat) to 2 (sharp)."
(Not -2 (sharp) to 2 (flat).)
Thank you, ƒg
___
bu
% Using the snippet below (from the official webpage), when I added a
measure rest at
% the beginning of Coda, an additional measure rest is printed out the
staff (close to "D.S...").
% It doesn't happen in the equivalent snippet from version 2.18.2.
\version "2.24.0"
{
\relative c'' {
c4 c
ut which are important and which are just
> notes.
Can you share the issues you've had with the official installation
instructions please?
The MacPorts package is not only out of our control, but also
broken (it's missing fonts), and they haven't fixed it in
almost a year (sigh). If
ons if necessary.
> I installed MacPorts which had some issues (beyond your control) to
> use that installer, and it appears I've finished, but the list of
> notes is extensive and I thought I'd share that with you. [...]
You can ignore all of them, they are not relevant, AFAIK
> Am 16.01.2024 um 12:37 schrieb Werner LEMBERG :
>
. . .
>
> You can ignore all of them, they are not relevant, AFAIK. The only
> issue with the 'lilypond' and 'lilypond-devel' bundles from MacPorts
> is what Jean has mentioned:
>
> https://tra
lilypond-book accepts --loglevel=WARN, but not --loglevel=WARNING.
I think WARN is for lilypond, not lilypond-book (according to the
documentation), so maybe just misdocumented?
Using 2.24.3
Thank you,
C
>> lilypond-book --loglevel=WARN book.lytex
> lilypond-book: error: file
I noticed a problem with `lilypond-book' (lilypond 1.5.68) when using the
--outdir option: the program halts while reading the following tex file:
\documentclass[a4paper]{article}
\begin{document}
\begin{lilypond}
\
What has happened to the stem lenght of half notes,
they are ridiculously long in 1.5.69.
/Mats
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
[EMAIL PROTECTED] writes:
> What has happened to the stem lenght of half notes,
> they are ridiculously long in 1.5.69.
already fixed in cvs.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Bug-lilypond m
Hello,
I imagine my .ly file contains some mistakes I have to correct, but as
Lily segfault, I suppose you will be interested...
I send you log and source as attached piece.
Feel free to ask for more details.
Thanks for developing lilypond :-)
Alex.
Script started on Fri Sep 13 14:20:05
The standard solution in these situations, is to define separate
identifiers for the different parts and then just make different
\score sections for the different versions of the music, see for
example the section "An orchestral score" in the Tutorial.
/Mats
Karl Berry wrote:
Doe
That's a clear bug in my opinion. The include path should be
set to include the directory of the file specified in the
argument of \lilypondfile{}.
/Mats
Jozsa Marton wrote:
I use lilypond-book to make a songbook.
All of my songs are in their own directory, and all of them contains the
enhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
It seems that when a midi block is present, a paper block must also be
present.
So include a paper block:
\score {
\midi {...}
\paper {}
}
Bert
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
Hello.
Is it possible to have a .ps or .pdf version of Lilypond 2.1 program
reference? I want to print it but tools like html2ps produce a ugly
output, expecially because it can't make a good table of contents (so
500 pages without a good ToC or index become quite unuseful).
Thank you.
Lud
Whenever I invoke lilypond-book on an HTML file, it
keeps saying that the file does not exist.
- [EMAIL PROTECTED]
PS Thanks for your previous help.
Yahoo! India Matrimony: Find your partner online.
Go to http
bin0.bin
Description: cialisontent_type
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
lilypond-book -> Music Fragment options
documents the option: filename="filename"
But the quotes cause an error. It only works as
instead of
Here is the error:
:1:24: error: parse error, expecting `'='':
\renameinput ""filename"
[EMAIL PROTECTED] writes:
> lilypond-book -> Music Fragment options
> documents the option: filename="filename"
>
> But the quotes cause an error. It only works as
>
> instead of
>
>
> Here is the error:
>
> :1:24: error: parse err
- What platform do you use (Windows, Linux (what distribution),
MacOS, ...)?
- How did you install it?
- What does the following command return?
lilypond-bin -V -h
(Please respond to the mailing list, not to me personally.)
/Mats
Bob Smith wrote:
I received the following error while trying to
When processing a file for latex use, LilyPond is now creating a *.tex
file rather than a *.latex file. This happens even if the
--format=latex option is explicitely given.
LilyPond 2.1.23 (CVS ChangLog level 1.718)
-David Bobroff
___
Bug-lilypond
I emailed earlier with problems compiling and installing Lilypond 2.2 on
SuSE 9.0. I have sucessfully compiled and installed and run version 2.0,
but still have trouble with 2.2. So, it's not a SuSE thing I think, but
possibly a problem in the code, or I don't have a recent enough ve
you with bug
reports?
Added crash-no-notes as something to start with:
%crash
%
\header {texidoc = "Lilypond crashes when there is no \\notes block in a
\\score" }
\version "2.3.4"
\score { }
___
bug-lilypond mailin
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 list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
I tried to compile the latest CVS version but get
make[1]: Entering directory `/space/lilypond/lily'
bison -o./out/parser.cc -d parser.yy
parser.yy:586: invalid input: `;'
make[1]: *** [out/parser.hh] Error 1
/Mats
Han-Wen Nienhuys wrote:
LilyPond 2.3.9 is up. The important chan
fixde in cvs.
[EMAIL PROTECTED] writes:
> I tried to compile the latest CVS version but get
>
> make[1]: Entering directory `/space/lilypond/lily'
> bison -o./out/parser.cc -d parser.yy
> parser.yy:586: invalid input: `;'
> make[1]: *** [out/parser.hh] Error 1
Thanks for the quick fix of parser.yy.
Next bug, the short options are printed with their ASCII value
instead of the character:
$$>lilypond -h
Usage: lilypond-bin [OPTIONS]... FILE...
Typeset music and/or produce MIDI from FILE.
LilyPond produces beautiful music notation.
For more information,
Hey there,
I run a pc with W2000, I have Cygwin installed already.
Unfortunately I use a 56k telephone connection, so my question is:
Is there a non-cygwin included download of Lilypond which I can integrate with
the already installes Cygwin?
have a good day,
Hans Sodaar
Of course, I should have cross-posted already the previous email to
bug-lilypond.
I just came to think of yet another possible solution, namely to
mimic the \verb command in LaTeX and let the user himself find a
character to use as start and end of the example that's not included
in the Lil
Citerar Mats Bengtsson <[EMAIL PROTECTED]>:
> Of course, I should have cross-posted already the previous email to
> bug-lilypond.
>
> I just came to think of yet another possible solution, namely to
> mimic the \verb command in LaTeX and let the user himself find a
> c
Are you saying that the trick used in \verb is bad or just that
we should never mention the example below in any documentation
or that we should use the \verb trick but handle pairing characters
specially?
/Mats
Werner LEMBERG wrote:
\lilypond{c d e f{
Of course, the final example looks
Werner
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
implementors will suffer. A direct
implementation of the \verb trick is a one line change (see the
attachment), whereas your suggestion is much harder to implement without
major surgery to the current lilypond-book implementation.
I won't submit the patch to CVS until I get some approval (of c
ed.
Werner
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ers
> >>specially?
> >
> >
> > The last one. All editors will benefit.
>
> Agreed! Unfortunately, the implementors will suffer. A direct
> implementation of the \verb trick is a one line change (see the
> attachment), whereas your suggestion is mu
> Well, I don't object to your simple implementation, I just suggest
> that a warning should be added to the docs that paired characters
> should be avoided.
Should be `pairing characters', of course.
Werner
___
bug-lilypond
Werner's suggestion was to allow for both
\lilypond+c d e f+
and
\lilypond{c d e f}
(of course, it can be done with a fairly simple regular expression
including an 'or', however it grows fairly quickly with the number of
pairing characters to support).
/Mats
Han-Wen Nienhuy
Jan Nieuwenhuizen wrote:
Graham Percival writes:
Why do we need to have \lilypond{}, anyway? I mean, what's
wrong with
\begin{lilypond}
\end{lilypond}
The initial idea (now broken in lilypond-book) was for \lilypond{}
to be a friendly way to get inline notes, without parskip and whatnot.
T
On Wednesday 13 October 2004 10.22, Mats Bengtsson wrote:
> >>It just seems to me that maintaining \lilypond{} is more trouble than
> >>it's worth.
> >
> > I think it just broke because of the lilypond-book rewrite, and the
> > decision to require [f
[EMAIL PROTECTED] writes:
> Citerar Mats Bengtsson <[EMAIL PROTECTED]>:
>
> > Of course, I should have cross-posted already the previous email to
> > bug-lilypond.
> >
> > I just came to think of yet another possible solution, namely to
> > mimic t
> \lilypond{c d e f{
>
> Of course, the final example looks ridiculous, but it's kind of
> logical anyway, once you've grasped the main idea.
Don't do that! A much better solution is to avoid pairing characters
(), {}, [] altogether -- or support them i
Hi,
There's a small typo in lily output:
When running lilypond --png, the output is as follows:
Parsing...
Interpreting music... [2]
Preprocessing graphical objects...
Calculating line breaks...
Layout output to `page-layout-two-pages.tex'...Converting to
`page-layout-two
Issue 671: In GUB binaries lilypond-book does not always call correct
lilypond binary
http://code.google.com/p/lilypond/issues/detail?id=671
New issue report by john.mandereau:
In GUB binaries, lilypond-book invokes /usr/bin/lilypond if it exists
instead of invoking lilypond binary from GUB
Issue 671: In GUB binaries lilypond-book does not always call correct
lilypond binary
http://code.google.com/p/lilypond/issues/detail?id=671
Comment #1 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Low devel-help
New issue 777 by gpermus: python script for indenting lilypond files
http://code.google.com/p/lilypond/issues/detail?id=777
It would be nice if there was a python script to indent lilypond files.
--
You received
Comment #1 on issue 777 by wbsoft: python script for indenting lilypond
files
http://code.google.com/p/lilypond/issues/detail?id=777
http://code.google.com/p/lilykde/source/browse/trunk/frescobaldi/python/ly/indent.py
--
You received this message because you are listed in the owner
or CC
Updates:
Labels: -devel-help Maintainability
Comment #2 on issue 777 by gpermus: python script for indenting lilypond
files
http://code.google.com/p/lilypond/issues/detail?id=777
(No comment was entered for this change.)
--
You received this message because you are listed in the
Updates:
Status: Fixed
Labels: fixed_2_13_3
Comment #54 on issue 504 by pnorcks: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or
Comment #55 on issue 504 by marnenlk: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Hallelujah! 2.13.3 does indeed work properly on Leopard. I'm glad to have
the IDE back -- it's about the only
way working with Lily has been feasi
Comment #56 on issue 504 by percival.music.ca: lilypond broken on osx 10.5
x86
http://code.google.com/p/lilypond/issues/detail?id=504
We shouldn't mention this until it's backported to the stable 2.12 version,
and that
in itself is waiting for other build fixes.
Besides, I be
Comment #57 on issue 504 by marnenlk: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Well, at the moment, even the Leopard download link for 2.13.3 goes to
Ivo's page which says that you can't
double-click Lily on Leopard. We should make clear
Comment #58 on issue 504 by wu.renfan: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
maybe another entry on the download-page -- 10.5 (leopard) go here... and
10.6 (Snow
Leopard). This would also make sure that Snow Leopardians would try the dev
Status: Accepted
Owner: percival.music.ca
Labels: Type-Documentation Priority-Postponed
New issue 851 by percival.music.ca: instructions for lilypond files in
texshop
http://code.google.com/p/lilypond/issues/detail?id=851
http://lists.gnu.org/archive/html/lilypond-user/2009-01/msg00293.html
Updates:
Status: Verified
Comment #59 on issue 504 by v.villenave: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
(Snow Leopard support seems to be in pretty good shape compared to the 10.5
mess.)
http://lists.gnu.org/archive/html/bug-lilypond
Status: Accepted
Owner: percival.music.ca
Labels: Type-Enhancement Priority-Medium Maintainability
New issue 867 by percival.music.ca: lilypond-book can have hash collisions
http://code.google.com/p/lilypond/issues/detail?id=867
It would be nice if lilypond-book checked if a filename already
Status: Accepted
Owner: percival.music.ca
Labels: Type-Other Priority-High
New issue 954 by percival.music.ca: GUB add temporary patch to lilypond
http://code.google.com/p/lilypond/issues/detail?id=954
Item for myself:
We need a mechanism to add a patch to the lilypond source tree before
Status: Accepted
Owner:
CC: john.mandereau
Labels: Type-Scripts Priority-Medium
New issue 1084 by pnorcks: lilypond-book fails on identical snippets
http://code.google.com/p/lilypond/issues/detail?id=1084
For details, please see the discussion here:
http://lists.gnu.org/archive/html/bug
Status: Accepted
Owner:
Labels: Type-Other Priority-Medium Maintainability Frog
New issue 1236 by percival.music.ca: CG+scripts should use ~/lilypond-git/
http://code.google.com/p/lilypond/issues/detail?id=1236
lily-git.tcl creates a repository in ~/lilypond-git/
All scripts should be
Comment #1 on issue 1281 by julien.rioux: enhancement: lilypond-book safe
mode
http://code.google.com/p/lilypond/issues/detail?id=1281
I'm providing a simple patch for this.
Attachments:
safe-mode.patch 1.4 KB
___
bug-lilypond ma
Updates:
Status: Fixed
Labels: Patch fixed_2_13_37
Comment #2 on issue 1281 by percival.music.ca: enhancement: lilypond-book
safe mode
http://code.google.com/p/lilypond/issues/detail?id=1281
Thanks, it looks fine. I've pushed it as
a672bdf4929d3cca8eec06a58e0ad7982fa
Updates:
Status: Verified
Comment #3 on issue 1281 by brownian.box: enhancement: lilypond-book safe
mode
http://code.google.com/p/lilypond/issues/detail?id=1281
This produces no errors (tried with 2.13.38):
lilypond-book --output=out --safe test.lytex
So, verified
Comment #1 on issue 1074 by bernieth...@gmail.com: -q quiet mode for
lilypond
http://code.google.com/p/lilypond/issues/detail?id=1074
This is something I could look at if anyone can tell me where to start!
___
bug-lilypond mailing list
bug
Status: Accepted
Owner:
Labels: Type-Other Priority-Medium Maintainability
New issue 1595 by percival.music.ca: lilypond-book papersize gives margin
warnings
http://code.google.com/p/lilypond/issues/detail?id=1595
Trying to compile the regtest added here:
http://git.savannah.gnu.org
Comment #1 on issue 1675 by v.villen...@gmail.com: lilypond as an html5 app
http://code.google.com/p/lilypond/issues/detail?id=1675
What you're referring to is GTK3's HTML5 "Broadway" backend, that's being
developed by Alex Larsson:
http://blogs.gnome.org/alexl/c
Updates:
Labels: Patch-review
Comment #1 on issue 1706 by percival.music.ca: Beaming causes lilypond to
crash
http://code.google.com/p/lilypond/issues/detail?id=1706
http://codereview.appspot.com/4662047/
___
bug-lilypond mailing list
bug
Updates:
Status: Fixed
Comment #2 on issue 1706 by mts...@gmail.com: Beaming causes lilypond to
crash
http://code.google.com/p/lilypond/issues/detail?id=1706
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug
Updates:
Labels: -Patch-review fixed_2_15_3
Comment #3 on issue 1706 by percival.music.ca: Beaming causes lilypond to
crash
http://code.google.com/p/lilypond/issues/detail?id=1706
(No comment was entered for this change.)
___
bug-lilypond
Comment #4 on issue 1706 by x.sche...@gmail.com: Beaming causes lilypond to
crash
http://code.google.com/p/lilypond/issues/detail?id=1706
May I suppose every critical regression like this one will be
cherry-picked in 2.14?
___
bug-lilypond
Updates:
Labels: backport
Comment #5 on issue 1706 by percival.music.ca: Beaming causes lilypond to
crash
http://code.google.com/p/lilypond/issues/detail?id=1706
No. Not unless it's marked backport.
___
bug-lilypond mailing lis
On 6/27/11 7:12 AM, "lilyp...@googlecode.com"
wrote:
>
>
> Comment #4 on issue 1706 by x.sche...@gmail.com: Beaming causes lilypond to
> crash
> http://code.google.com/p/lilypond/issues/detail?id=1706
>
> May I suppose every critical regression like this one
Updates:
Status: Verified
Comment #6 on issue 1706 by lilyli...@googlemail.com: Beaming causes
lilypond to crash
http://code.google.com/p/lilypond/issues/detail?id=1706
In 2.15.3 there still are many error messages (identical to the one quoted
in the original post),
but Lilypond
Comment #7 on issue 1706 by n.putt...@gmail.com: Beaming causes lilypond to
crash
http://code.google.com/p/lilypond/issues/detail?id=1706
Anybody else getting beam-skip.ly showing up in every regtest comparison?
I assume it's not showing up between builds since they aren't com
Updates:
Labels: -backport fixed_2_14_2
Comment #8 on issue 1706 by carl.d.s...@gmail.com: Beaming causes lilypond
to crash
http://code.google.com/p/lilypond/issues/detail?id=1706
Backported
___
bug-lilypond mailing list
bug-lilypond
Comment #9 on issue 1706 by carl.d.s...@gmail.com: Beaming causes lilypond
to crash
http://code.google.com/p/lilypond/issues/detail?id=1706
You will make it much easier to backport if you will include a commit
number in the comment when you change the status to fixed.
Thanks,
Carl
Updates:
Labels: -Patch-review Patch-needs_work
Comment #1 on issue 1727 by colinpkc...@gmail.com: Adds glissando stems to
lilypond
http://code.google.com/p/lilypond/issues/detail?id=1727
(No comment was entered for this change.)
___
bug
Status: Accepted
Owner: mts...@gmail.com
Labels: Type-Defect Priority-Critical Patch-new
New issue 1796 by mts...@gmail.com: LilyPond segfaults on make-footer = ##f
http://code.google.com/p/lilypond/issues/detail?id=1796
\version "2.15.7"
\paper { make-footer = ##f }
\
Comment #1 on issue 1815 by uwestoeh...@gtempaccount.com: lilypond-book
fails on Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
A colleague of mine working under Linux does not see the bug, so my guess
that the (back)slash issue might trigger this can be the bug
Updates:
Status: Accepted
Labels: Type-Scripts Priority-Medium OpSys-Windows
Comment #2 on issue 1815 by philehol...@googlemail.com: lilypond-book fails
on Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
(No comment was entered for this change
Updates:
Status: Fixed
Labels: -Frog fixed_2_15_9
Comment #2 on issue 1074 by k-ohara5...@oco.net: -q quiet mode for lilypond
http://code.google.com/p/lilypond/issues/detail?id=1074
Fixed with Reinhold's fix to 1790
The option
Updates:
Status: Verified
Comment #3 on issue 1074 by brownian.box: -q quiet mode for lilypond
http://code.google.com/p/lilypond/issues/detail?id=1074
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond
Comment #3 on issue 1815 by julien.r...@gmail.com: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
Suggested patch
Attachments:
1815-lilypond-book-on-windows.patch 758 bytes
___
bug-lilypond
Updates:
Labels: Patch-new
Comment #4 on issue 1815 by percival.music.ca: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
Thanks! what version of git did you use? I'm having trouble committing it
to my local tree. I could just
Comment #5 on issue 1815 by julien.r...@gmail.com: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
Ah! I used git show HEAD > patch
Sorry I'm new to git. Here's the patch in the way you suggested.
Attachments:
0001-Fix-issue-1815-
Updates:
Labels: -Patch-new fixed_2_15_11
Comment #6 on issue 1815 by percival.music.ca: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
thanks, pushed
___
bug-lilypond mailing list
bug-lilypond
Updates:
Status: Fixed
Comment #7 on issue 1815 by percival.music.ca: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug
Issue 485: please make #(ly:export(lilypond-version) safe
http://code.google.com/p/lilypond/issues/detail?id=485
New issue report by gpermus:
It would be nice if there was a "safe" (ie lilypond -dsafe) command that
did #(ly:export(lilypond-version). This would reduce the numbe
Issue 485: please make #(ly:export(lilypond-version) safe
http://code.google.com/p/lilypond/issues/detail?id=485
Comment #1 by hanwenn:
Can you give more context? .ly snippet please.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Issue 485: please make #(ly:export(lilypond-version) safe
http://code.google.com/p/lilypond/issues/detail?id=485
Comment #2 by gpermus:
%{
This example is flagged as `unsafe'.
%}
%% Do not edit this file; it is auto-generated from LSR!
\header{
texidoc = "
@unnumbered Ancient M
On 6 Nov 2007, at 02:59, [EMAIL PROTECTED] wrote:
Issue 504: lilypond broken on osx 10.5
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #6 by hanwenn:
There is a command-line binary in LilyPond.app/Contents/Resources/
bin/lilypond
Can anyone verify whether that one works
On 18 Nov 2007, at 21:51, [EMAIL PROTECTED] wrote:
Issue 504: lilypond broken on osx 10.5
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #16 by gpermus:
Let me clarify Han-Wen's comment:
*NOBODY* on the development team has OSX 10.5. *NOBODY* on the
development tea
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #22 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Summary: lilypond broken on osx 10.5 x86
--
You received this message because you are listed in
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #23 by haggardii:
wait, hanwenn... the stable version of lilypond is broken on PPC too,
not just the
x86. chhitz is referring to only the command-line version of lilypond
-- and it'
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #24 by wu.renfan:
ONLY the commandline version of 2.11.35-2 (dev) of the PPC-binary works
on 10.5.1 --
actually, it seems regardless if you use it on a PPC or an Intel. The x86-binary
2.11
Issue 485: please make #(ly:export(lilypond-version) safe
http://code.google.com/p/lilypond/issues/detail?id=485
Comment #3 by joeneeman:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_36
--
You received this message because
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #25 by ivo.bouwmans:
Would it be possible to indicate this problem on the Lilypond download
page (or
remove "and newer" from "10.4 and newer"), so that Leopard users
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #26 by hanwenn:
changed on download page.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #27 by jellyfish.cory:
By the way, I noticed one or two comments on here (most notably #20)
instruct the user to
make
sudo make install
Macs don't come with GNU make, and GNU
Issue 504: lilypond broken on osx 10.5 x86
http://code.google.com/p/lilypond/issues/detail?id=504
Comment #28 by hanwenn:
unfortunately, I don't see any easy way to fix this. I invite people
to complain the
correct people about this (probably: odcctools development.)
Issue attribute up
401 - 500 of 3441 matches
Mail list logo
