Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
On 18-Aug-05, at 7:21 AM, John Mandereau wrote:
When I tried to run 2.6.3 midi2ly on Fedora Core 4, I got:
Traceback (most recent call last):
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Thanks for looking into this, but this will probably break when doing:
>
> CC=gcc-3.4 CXX=g++-3.4 ./configure
Yep, it did break.
> I'm not exactly sure what to do. Probably first sed-out everything in
> parentheses.
I think this will work.
P
Pedro Kröger writes:
> # gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)
Aargh.
> The small patch attached seems to fix it, but I tested it only in cygwin
> and in my debian box.
Thanks for looking into this, but this will probably break when doing:
CC=gcc-3.4 CXX=g++-3.4 .
Daniel Johnson wrote:
Hello all --
I know that MIDI output was broken under 2.7.5 (and 2.7.6?). Is it
functional under 2.7.7? I'm running the 2.7 series now and I'd prefer
not to have to do a parallel installation of 2.6 just for the sake of MIDI.
I also take sponsorship for bugfixes, by t
On Wednesday 24 August 2005 08.59, Daniel Johnson wrote:
> Hello all --
>
> I know that MIDI output was broken under 2.7.5 (and 2.7.6?). Is it
> functional under 2.7.7? I'm running the 2.7 series now and I'd prefer
> not to have to do a parallel installation of 2.6 just for the sake of MIDI.
A q
Hello all --
I know that MIDI output was broken under 2.7.5 (and 2.7.6?). Is it
functional under 2.7.7? I'm running the 2.7 series now and I'd prefer
not to have to do a parallel installation of 2.6 just for the sake of MIDI.
--Daniel
___
lilypo
