I've found a strange thing (looks like a cygwin issue, because it is
corrected in the snapshot):
When double-clicking it gives an error message (unable to remap some
DLL).
But when I changed lily-wins to a sh script containing:
#!/bin/sh
python /bin/lily-wins.py $1
it worked.
So I changed it in t
> That is very good news. Thanks for trying snapshots. Did you ack
> that on the Cygwin list, they might want to know the issue is closed
> by some snapshot.
Yes.
> Oh, another thing. There was a thread here, yesterday, about how
> double clicking on a .ly file with errors is not a friendly
> e
Fodor Bertalan writes:
> It seems that the problem is solved in the last cygwin snapshot, so I
> was able to build 2.2.0.
That is very good news. Thanks for trying snapshots. Did you ack
that on the Cygwin list, they might want to know the issue is closed
by some snapshot.
> I will test it an
It seems that the problem is solved in the last cygwin snapshot, so I
was able to build 2.2.0.
I will test it and send to cygwin mirrors if it's ok.
Bert
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-
Bertalan Fodor writes:
>> Possibly, I think you should asking the Cygwin list?
> I got an answer:
>
> "It's an unresolved issue that needs someone to help with tracking it down.
> If you're so inclined, build a debug version of the Cygwin DLL and check
> it out."
>
> Perhaps some time I will do t
Bertalan Fodor writes:
>> Possibly, I think you should asking the Cygwin list?
> I got an answer:
>
> "It's an unresolved issue that needs someone to help with tracking it down.
> If you're so inclined, build a debug version of the Cygwin DLL and check
> it out."
>
> Perhaps some time I will do t
> Possibly, I think you should asking the Cygwin list?
I got an answer:
"It's an unresolved issue that needs someone to help with tracking it down.
If you're so inclined, build a debug version of the Cygwin DLL and check
it out."
Perhaps some time I will do this. In these days I have very few ti
Bertalan Fodor writes:
> Program exited normally, no crash when in gdb.
>
> When not in gdb it crashes.
Hmm, that's fishy.
> Is it a cygwin issue?
Possibly, I think you should asking the Cygwin list?
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://w
Program exited normally, no crash when in gdb.
When not in gdb it crashes.
However, when running with strace I've found something interesting:
144 20792388 [main] lilypond-bin 1000 seterrno_from_win_error:
/netrel/src/cygwin-1.5.9-1/winsup/cygwin/cygheap.cc:219 windows error 487
321 20792709
Bertalan Fodor writes:
> OK, it runned at crashed at some other place.
Good.
> How can I trace it with gdb?
You start gdb with lilypond-bin, and then type: run
Then you wait for a crash, and type: bt
So, do:
export LILYPONDPREFIX=/netrel/build/lilypond-2.2.0/share/lilypond
gdb -nw /n
OK, it runned at crashed at some other place.
How can I trace it with gdb?
paper output to `lily-193070645.tex'...
Segmentation fault (core dumped)
Bert
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond
Bertalan Fodor writes:
> ERROR: In procedure primitive-load-path:
> ERROR: Unable to find file "lily.scm" in load path
>
> (The same happened when I replaced the 2.1.31 executable with the 2.2.0 )
Ah, of course. You must tell Lily where to find all external files,
try adding the LILYPONDPREFIX s
ERROR: In procedure primitive-load-path:
ERROR: Unable to find file "lily.scm" in load path
(The same happened when I replaced the 2.1.31 executable with the 2.2.0 )
> What happens when you type:
>
> /netrel/build/lilypond-2.2.0/lily/out/lilypond-bin -e
> '(ly:set-option (quote internal-typ
Bertalan Fodor writes:
> Signal 11 while building doc, I've attached parts of the log (dropped
> font-creating log).
I can't reproduce this. lilypond-bin crashes when building a lot of
example files. You should try to find the command that causes the
crash. Once you have that, you can use gdb
14 matches
Mail list logo
