On Sat, Dec 23, 2000 at 01:46:17PM -0700, Anthony Fok wrote:
> For some reasons, the --force wasn't there during the build, so it just
> stopped there (and I had to restart the build). But when I ran make again,
> without "make distclean", the --force was there and after some warning
> messages it continues on merrily. Strange. But then this computer I am
> using is really acting up too... segfaulting and kernel oopsing/panicking
> erratically that I simply couldn't finish the build without being stopped at
> random places. So I ended up using my brother's computer to build
> lilypond1.3_1.3.119-1. Besides, his computer is so much faster. :-)
My experience on building lily is that the current debian unstable g++
produces a binary that segfaults; debian stable g++ compiles it fine,
which leads me to suspect that g++ is at fault, rather than lilypond
itself. Since I barely read C++, let alone write it, that should be
treated only as a suspicion. This was reproduceable across different
computers, incidentally, so it's probably not just a random glitch.
Cheers,
Christophe
--
Jesus College, Cambridge, CB5 8BL +44 1223 524 842
(FORMAT T "(~@{~w ~}~3:*'~@{~w~^ ~})" 'FORMAT T "(~@{~w ~}~3:*'~@{~w~^ ~})")
_______________________________________________
Gnu-music-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/gnu-music-discuss
