[kaffe] libtritonusalsa does not get installed

Dalibor Topic robilad@kaffe.org
Sun Jan 18 12:07:01 2004


Hallo Matthias,

Matthias Pfisterer wrote:

> First the "no target all in po" that was reported recently. I edited the 
> top-level Makefile to remove po from SUBDIRS as suggested.

This should be fixed now [1]. Could you do a fresh check out from CVS 
and retry?

> Now I get the following:
> -- 
> Making all in libraries/javalib
> make[1]: Entering directory `/home/matthias/java/kaffe/libraries/javalib'
> rm -rf lib
> mkdir lib
> /bin/sh ./rebuildLib @essential.files
> Compiling classes from  @essential.files  using 
> /home/matthias/java/kaffe/kaffe/kaffe/kaffe-bin -verbosegc -mx 256M 
> at.dms.kjc.Main
> [ start compilation in verbose mode ]
> [ parsed gnu/classpath/Configuration.java in 486 ms ]
> ./rebuildLib: line 58: 15924 Segmentation fault      $JAVAC $VERBOSE 
> $JAVAC_FLAGS -d $LIBDIR $CPATH ${1+"$@"}
> make[1]: *** [lib/stamp] Error 139
> make[1]: Leaving directory `/home/matthias/java/kaffe/libraries/javalib'
> make: *** [all-recursive] Error 1
> -- 
> This is for ./configure without opions. If I say './configure 
> --without-alsa', the following happens:
> -- 
> make[1]: Entering directory `/home/matthias/java/kaffe/libraries/javalib'
> rm -rf lib
> mkdir lib
> /bin/sh ./rebuildLib @essential.files
> Compiling classes from  @essential.files  using 
> /home/matthias/java/kaffe/kaffe/kaffe/kaffe-bin -verbosegc -mx 256M 
> at.dms.kjc.Main
> [ start compilation in verbose mode ]
> [ parsed gnu/classpath/Configuration.java in 471 ms ]
> -- 
> ...and it hangs, hogging the CPU. It is interruptible with ctrl-C.

Interesting bugs, definitely. I'd be more interested in the crash, atm. 
Do the problems still occur with the current version from CVS HEAD? If 
so, what's your cpu-os platform (or distribution, of you are using 
linux), and which gcc are you using? Are there any interesting warnings 
during compilation?

cheers,
dalibor topic

[1] Well, some problems with make dist remain, but I'm looking into it. 
It seems like using GNU gettext is a good recepe for spending a weekend 
chasing weird build failures. :(