On Thu, 29 Aug 2013, Zack Macomber wrote:
I have several Finale Allegro 2007 compositions that I would like to see in
LilyPond. I can save my compositions as a MIDI file. When I drag that MIDI
file onto the LilyPond shortcut on my desktop, a file gets written to where
the MIDI file is with t
I have several Finale Allegro 2007 compositions that I would like to see in
LilyPond. I can save my compositions as a MIDI file. When I drag that MIDI
file onto the LilyPond shortcut on my desktop, a file gets written to where
the MIDI file is with this message in it:
# -*-compilation-*-
Proc
"Mark Polesky" wrote in message
news:1377680573.29275.yahoomail...@web181405.mail.ne1.yahoo.com...
Werner Lemberg wrote:
Can you show us the lines in your `make.log' file directly
after the calls to the `pfx2ttf.fontforge' script? Maybe
there is some hint which shows what's going on.
Curiousl
David Kastrup wrote:
>> make all &> make.log
>>
>> Am I using the wrong redirection operator?
>
> Depends on your shell. Bash understands both &> and >&.
Well, I'm using bash. This just gets weirder and weirder.
Here's my make.log:
http://www.markpolesky.com/norobots/make.log
___
Mark Polesky writes:
> Werner Lemberg wrote:
>> Can you show us the lines in your `make.log' file directly
>> after the calls to the `pfx2ttf.fontforge' script? Maybe
>> there is some hint which shows what's going on.
>
> Curiously, no. There is no call to that function in my
> make.log file.
Werner Lemberg wrote:
> Can you show us the lines in your `make.log' file directly
> after the calls to the `pfx2ttf.fontforge' script? Maybe
> there is some hint which shows what's going on.
Curiously, no. There is no call to that function in my
make.log file. I did:
make all &> make.log
Am
Thomas Klausner writes:
> I see you replied to my build issue in lilypond-2.17.24 that I should
> try a clean build.
>
> I've done that. I built versions 2.17.23, 2.17.24, and 2.17.25 from
> scratch in a sandbox, in different directories, and I still see this
> issue, in 2.17.24 and 2.17.25, but
> are you implying that you might know how to fix this?
Not really. Actually, I hope that some of our make gurus chime in :-)
Can you show us the lines in your `make.log' file directly after the
calls to the `pfx2ttf.fontforge' script? Maybe there is some hint
which shows what's going on.
hello,
>> I've tried that but see a new error while generating documentation:
>>
>>
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/ly/chord-modifiers-init.ly:26:4:
error: syntax error, unexpected REAL
>> <
>>c e gis>1-\markup { "+" }
>
> Nothing t
Hi David!
I see you replied to my build issue in lilypond-2.17.24 that I should
try a clean build.
I've done that. I built versions 2.17.23, 2.17.24, and 2.17.25 from
scratch in a sandbox, in different directories, and I still see this
issue, in 2.17.24 and 2.17.25, but not in 2.17.23.
Also, I'v
Werner Lemberg wrote:
> Note that there seems to be a bug somewhere regarding
> dependencies: Doing a non-parallel build, the above
> command is run four times. Maybe this is the very reasons
> of your problem.
Werner,
are you implying that you might know how to fix this? Or
should I instead as
11 matches
Mail list logo
