On Wed, Jun 30, 2004, Karl Vogel wrote:

> PING! :-)

<grin> Thanks for knocking, Karl. Yes, I was not sure about this issue
last time and so I did some other issues in the meantimes...

> > The automake package removes all the files in %{l_prefix}/bin/*-*
> >
> > This is incorrect, as the 'missing' script of automake/autoconf uses
> > the versioned binaries to automatically re-run automake if the .am
> > files are altered.
> >
> > Hmm this sounds complicated..  example session:
> >
> > $ make
> > make  all-recursive
> > make[1]: Entering directory `/usr/users/kvo/obj'
> > Making all in src
> > make[2]: Entering directory `/usr/users/kvo/obj/src'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/usr/users/kvo/obj/src'
> > make[2]: Entering directory `/usr/users/kvo/obj'
> > make[2]: Nothing to be done for `all-am'.
> > make[2]: Leaving directory `/usr/users/kvo/obj'
> > make[1]: Leaving directory `/usr/users/kvo/obj'
> > [dev:medusa] ~/obj
> >
> > >> Everything is up to date, so nothing is done by make.
> > >> now touch an input automake file:
> >
> > $ touch ../Makefile.am
> > [dev:medusa] ~/obj
> > $ make
> >  cd .. && /bin/ksh /usr/users/kvo/missing --run automake-1.8 --foreign
> > Makefile
> >  cd . && /bin/ksh ./config.status Makefile
> > config.status: creating Makefile
> > make  all-recursive
> > make[1]: Entering directory `/usr/users/kvo/obj'
> > Making all in src
> > make[2]: Entering directory `/usr/users/kvo/obj/src'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/usr/users/kvo/obj/src'
> > make[2]: Entering directory `/usr/users/kvo/obj'
> > make[2]: Nothing to be done for `all-am'.
> > make[2]: Leaving directory `/usr/users/kvo/obj'
> > make[1]: Leaving directory `/usr/users/kvo/obj'
> > [dev:medusa] ~/obj
> >
> > >> 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?

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   [EMAIL PROTECTED]

Reply via email to