Re: Error compiling 1.6.20 and 1.8.1

[Michael Edwards]

Hmm, I can't really.  I am able to use gcc 3.0.4 (unsuccessfully), but,
beyond that, it's a pretty major update to the system.  

The weird thing is, I get the compilation problem even with the stock
gcc and libc that come with the Redhat 7.3 distro.  I figure it's got to
be something else, then, since I know there are other people who've used
lilypond on RH 7.3--there's even an RPM (which, unfortunately, requires
a version of guile that conflicts with a lot of other software).

Anyone out there with RH 7.3 success stories?

-Mike

On Mon, 2003-08-25 at 14:04, Han-Wen Nienhuys wrote:
> address@hidden writes:
> > I get the same error when I try to compile either 1.6.12 or 1.8.1:
> > 
> > mv out/lilypond.texi out/lilypond.nexi
> > chmod -w out/lilypond.nexi
> > makeinfo --output=./out/lilypond.info out/lilypond.nexi
> > cd ./out && /home/edwards/tarballs/lilypond-1.6.12/lily/out/lilypond
> > --verbose
> > /home/edwards/tarballs/lilypond-1.6.12/ly/generate-documentation
> > make[2]: *** [out/lilypond-internals.nexi] Error 139
> > rm out/lilypond.nexi
> > make[2]: Leaving directory
> > `/home/edwards/tarballs/lilypond-1.6.12/Documentation/user'
> > make[1]: *** [all] Error 2
> > rm out/index.texi
> > make[1]: Leaving directory
> > `/home/edwards/tarballs/lilypond-1.6.12/Documentation'
> > make: *** [all] Error 2
> > 
> > It seemed to be a problem with the compiled binary.  Sure enough, when I
> > ran it, I got a seg fault.  Here's the backtrace I ran with gdb on
> > lilypond 1.6.12:
> > 
> > #0  0x0805208e in String_handle::~String_handle() (this=0xbffff6c0)
> >     at include/string-handle.icc:22
> > #1  0x080ecaaa in setup_paths() () at
> > ../flower/include/string-handle.icc:59
> > #2  0x080eff4c in main (argc=1, argv=0xbffff884) at main.cc:415
> > #3  0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
> > 
> > That's similar to what happened with 1.8.1--something with
> > string-handle.icc at line 22.
> > 
> > Any ideas?  I'm running Redhat 7.3, but I have upgraded a number of
> > different things, including guile (1.6.4).  I compiled 1.8.1 with gcc
> > 3.0 and 1.6.12 with gcc 2.96.  
> 
> We have reports of similar problems on similar platforms (ia64 with RH
> AS 2.1). We strongly suspect a GCC and/or libc (or libstdc++) bug.
> Are you able to update either libc or GCC to their latest versions and
> recompile?