[kaffe] kaffe build failure on cvs since 03/03

[Dalibor Topic]

Barry Hawkins wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> List,
> ~    Myself an another person on #kaffe are experiencing failure when
> trying to build kaffe from CVS on both x86 and ppp architectures.  I
> first noticed the problem on 03/03/2005.  The failure is the same on
> either platform.  At the behest of Dalibor Topic, I am posting the
> information to the list.  The configure statement for ppc (JIT disabled)
> and a transcript from x86 are attached below:
> 
> ppc configure statement:
> $ ./configure --with-jikes --with-engine=intrp --prefix=/usr/local/kaffe
> - --without-kaffe-qt-awt --without-kaffe-x-awt --enable-debug
> 
> x86 transcript:
> $ ./configure --with-jikes --prefix=/usr/local/kaffe
> - --without-kaffe-qt-awt --without-kaffe-x-awt --enable-debug
> $ make
> Making all in .
> make[1]: Entering directory `/usr/src/kaffe'
> make top_srcdir=`cd . >/dev/null; pwd` \
> ~        top_builddir=`cd . >/dev/null; pwd` \
> ~        "DEBUG_ENV=" BUILD_ENVIRONMENT-make
> make[2]: Entering directory `/usr/src/kaffe'
> echo
> BOOTCLASSPATH=\${BOOTCLASSPATH}\'':'\'/usr/src/kaffe/libraries/javalib/rt.jar\'':'\'\'':'\'\; 
> 
> export BOOTCLASSPATH | sed 's,/,/,g;s,\\,\\\\,g' > BUILD_ENVIRONMENT.new; \
> echo
> CLASSPATH=.\'':'\'\${GNU_CRYPTO_JAR}\'':'\'\${JAVAX_SECURITY_JAR}\'':'\'\'':'\'\'':'\'\; 
> 
> export CLASSPATH | sed 's,/,/,g;s,\\,\\\\,g' >> BUILD_ENVIRONMENT.new; \
> echo
> KAFFELIBRARYPATH=\${KAFFELIBRARYPATH+\"\$KAFFELIBRARYPATH\"\'':'\'}`for
> f in /usr/src/kaffe/libraries/clib/native/libnative.la
> /usr/src/kaffe/libraries/clib/net/libnet.la
> /usr/src/kaffe/libraries/clib/io/libio.la
> /usr/src/kaffe/libraries/clib/nio/libnio.la
> /usr/src/kaffe/libraries/clib/zip/libzip.la
> /usr/src/kaffe/libraries/clib/management/libmanagement.la
> /usr/src/kaffe/libraries/clib/security/libsecurity.la  ; do echo "$f" |
> sed 's%/[^/]*$%%'; done | (tr '\012' ' '; echo) | sed -e 's/ $//' -e "s/
> /\':\'/g"`\; export KAFFELIBRARYPATH >> BUILD_ENVIRONMENT.new; \
> echo JAVA=/usr/src/kaffe/kaffe/kaffe/kaffe-bin\; export JAVA >>
> BUILD_ENVIRONMENT.new; \
> echo
> LD_LIBRARY_PATH=/usr/src/kaffe/libraries/clib/classpath/.libs:\${LD_LIBRARY_PATH}\; 
> 
> export LD_LIBRARY_PATH >> BUILD_ENVIRONMENT.new;\
> echo
> DYLD_LIBRARY_PATH=/usr/src/kaffe/libraries/clib/classpath/.libs:\${DYLD_LIBRARY_PATH}\; 
> 
> export DYLD_LIBRARY_PATH >> BUILD_ENVIRONMENT.new
> rm -f BUILD_ENVIRONMENT
> mv BUILD_ENVIRONMENT.new BUILD_ENVIRONMENT
> make[2]: Leaving directory `/usr/src/kaffe'
> make[1]: Leaving directory `/usr/src/kaffe'
> Making all in libraries/javalib
> make[1]: Entering directory `/usr/src/kaffe/libraries/javalib'
> Making all in .
> make[2]: Entering directory `/usr/src/kaffe/libraries/javalib'
> make[2]: *** No rule to make target `gnu/bytecode/Access.java', needed
> by `lib/stamp'.  Stop.
> make[2]: Leaving directory `/usr/src/kaffe/libraries/javalib'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/kaffe/libraries/javalib'
> make: *** [all-recursive] Error 1

Hi Barry,

thanks for reporting this problem. I've discussed it with David 
Wallauck, who has the same issue, and Michael Koch. It seems that unless 
you use

cvs update -dP

you won't get the new files that were checked in, which makes the build 
to fail. Could you try again with the above command from the checked out 
source directory ?

cheers,
dalibor topic