Re: testing before a release

[Mark Wielaard]

Hi,

On Mon, Nov 05, 2001 at 09:43:57PM +0100, Mark Wielaard wrote:
> 
> I will update my build environment and report any progress on --enable-jni.
Ok with the latest packages it works on x86. (Well it compiles at least.)

Note to Debian GNU/Linux developers: automake 1.52 is in the package called
automake1.5, the 'normal' package automake contains the old 1.4-p4 version.
The package autoconf contains both autoconf 2.13 and autoconf 2.52.
To call the 2.52 version you seem to need to call the 2.50 versions.
So you would type:
        aclocal; autoheader2.50; automake; autoconf2.50
Then you have a configure script which you can call with
    ./configure --with-gcj --enable-jni
and just type
    make

I wasn't so lucky on Debian GNU/Linux powerpc. There I get errors like:

aclocal: configure.in: 109: macro `AM_PATH_GTK' not found in library
aclocal: configure.in: 110: macro `AM_PATH_GLIB' not found in library
aclocal: configure.in: 114: macro `AM_PATH_LIBART' not found in library
autoheader2.50: error: AC_CONFIG_HEADERS not found in configure.in
configure.in: 19: required file `././include/config.h.in' not found
lib/Makefile.am:40: USER_SPECIFIED_KJC does not appear in AM_CONDITIONAL
lib/Makefile.am:51: FOUND_JIKES does not appear in AM_CONDITIONAL
lib/Makefile.am:54: FOUND_GCJ does not appear in AM_CONDITIONAL
lib/Makefile.am:57: FOUND_KJC does not appear in AM_CONDITIONAL
/usr/share/automake/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
[...]

And the generated configure script just doesn't work iand dies with syntax
errors :(

Cheers,

Mark
-- 
Stuff to read:
    <http://www.toad.com/gnu/whatswrong.html>
  What's Wrong with Copy Protection, by John Gilmore