> > > >> automake-1.8 is automatically run by the generated Makefile.
> > >
> > > With the current RPM spec, the 'automake-1.8' doesn't exist.
>
> The point is this: we generally dislike versioned executables, so we
> removed the versioned one _AND_ patched Automake to no longer
> use them.
> So I guess the problem you have is that you have a Makefile
> generated by
> some non-OpenPKG Automake and now it cannot re-generate
> itself with the
> OpenPKG Automake, right? I guess that once you run "automake"
> manually,
> the Makefiles will work fine again, right?
Well I just tried that, but it doesn't seem to work either.
I checked out my sources, ran autogen.sh which does:
=============================
# autogen.sh
#
# invoke the auto* tools to create the configuration system
# copy aclocal
aclocal
# Make config.h.in
autoheader
# Create Makefile.in
automake --foreign --add-missing
# build the configure script
autoconf
# set up libtool
libtoolize --force
=============================
./configure'd the source.. then touch Makefile.am and then make, giving me:
WARNING: `automake-1.8' is missing on your system. You should only need it
if
you modified `Makefile.am', `acinclude.m4' or `configure.in'.
You might want to install the `Automake' and `Perl' packages.
Grab them from any GNU archive site.
Looking in the Makefile, I see that AUTOMAKE points to automake-1.8 and
ACLOCAL
points to aclocal-1.8
I'm using the following automake, autoconf combo:
$ openpkg rpm -q automake autoconf
automake-1.8.5-20040517
autoconf-2.59-20040429
I wonder if it's really a good idea to remove the versioning.. the
developers
must have had a reason to do it this way, no?!
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
