On Sat, Dec 23, 2000 at 10:15:18PM +0000, Christophe Rhodes wrote:
> > 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.
I guess I wasn't clear enough. My computer (this newer one anyway) was
segfaulting/oopsing/panicking and hanging up on its own especially during
time of much disk activity, e.g. when I try to open Netscape while opening a
large mailbox in mutt while compiling lilypond1.3. Fortunately, my
brother's computer didn't show any of these problem and compiled it quickly
without errors. The compiled lilypond_1.3.119 binary seems fine, otherwise
the documentation wouldn't have been built, and there wouldn't have been a
*.deb produced. :-)
I am suspecting either the kernel doesn't jive well with this CPU or
motherboard, or (I hope not) faulty RAM or hard drive... not sure what is
wrong...
Cheers,
Anthony
--
Anthony Fok Tung-Ling Civil and Environmental Engineering
[EMAIL PROTECTED], [EMAIL PROTECTED] University of Alberta, Canada
Debian GNU/Linux Chinese Project -- http://www.debian.org/intl/zh/
Come visit Our Lady of Victory Camp -- http://www.olvc.ab.ca/
_______________________________________________
Gnu-music-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/gnu-music-discuss
