[Gc]: Maintainers attention: libatomic_ops
hans.boehm at hp.com
Tue Oct 6 22:19:32 PDT 2009
I have to confess that I'm confused about the status (a common problem for me when dealing with autotools). Things more or less seem to work for me, though I'm still getting warnings and huge diffs during and after rerunning the autotools. Can someone summarize the recommended reconfiguration procedure?
My understanding is still that the only way we can avoid both complete standardization of reconfiguration procedure and large diffs is to remove things like Makefile.in and configure from cvs, which means that anyone wanting to build from cvs needs a complete set of autotools?
Especially since gcc apparently still checks in those files, and we've had too few releases recently, I'd still be inclined to leave build-essential files for now, if we can make it work tolerably.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Ivan Maidanski
> Sent: Friday, October 02, 2009 1:32 AM
> To: gc at napali.hpl.hp.com
> Subject: Re: [Gc]: Maintainers attention: libatomic_ops
> "Matthias Andree" <matthias.andree at gmx.de> wrote:
> > Am 01.10.2009, 09:37 Uhr, schrieb Ivan Maidanski <ivmai at mail.ru>:
> > > Hi!
> > >
> > > Petter Urkedal <urkedal at nbi.dk> wrote:
> > >> On 2009-10-01, Matthias Andree wrote:
> > >> > Am 30.09.2009, 19:32 Uhr, schrieb Petter Urkedal
> <urkedal at nbi.dk>:
> > >> > > On 2009-09-29, Boehm, Hans wrote:
> > >> > >> It looks like we're using automake 1.9.6 and autoconf 2.59?
> > >> > >
> > >> > > I believe that's the latest versions which are
> widely available.
> > >> >
> > >> > Not at all. Current versions are automake 1.10.2 and autoconf
> > >> > 2.64. I checked FreeBSD: automake 1.10.2 and autoconf 2.62;
> > >> > Ubuntu Hardy (the early 2008 long-term support
> release) already
> > >> > has the releases
> > >> suggested
> > >> > below, current openSUSE has 1.10.1 and autoconf 2.63;
> Fedora 11
> > >> > has autoconf 2.63 and automake 1.11.
> > >
> > > I've installed newest autoconf and automake. Now, autoreconf -vif
> > > (after deleting libtool.m4) fails with:
> > If you've installed those into a different path prefix than
> > that may be it.
> > > configure.ac:397: error: possibly undefined macro:
> > > If this token and others are legitimate, please use
> > > m4_pattern_allow.
> > > See the Autoconf documentation.
> > > configure.ac:471: error: possibly undefined macro: AC_PROG_LIBTOOL
> I've already solved the problem by installing libtool. Fetch
> the latest CVS.
> > Try forcing libtoolize and heed its warnings and suggestions
> > (unfortunately they are easily lost in the clutter).
> > Particularly, I'd suggest not to lump everything into
> > acinclude.m4/aclocal.m4 but use a separate m4/ directory as
> > will suggest.
> > --
> > Matthias Andree
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc