[Gc]: Maintainers attention: libatomic_ops
urkedal at nbi.dk
Thu Oct 1 14:40:22 PDT 2009
On 2009-10-02, Ivan Maidanski wrote:
> Petter Urkedal <urkedal at nbi.dk> wrote:
> > On 2009-10-01, Ivan Maidanski wrote:
> > > Ok. I've installed it, deleted libtool.m4 and run autoreconf -vif. It prints:
> > >
> > > libtoolize: You should add the contents of the following files to `aclocal.m4':
> > > libtoolize: `/usr/local/share/aclocal/libtool.m4'
> > > libtoolize: `/usr/local/share/aclocal/ltoptions.m4'
> > > libtoolize: `/usr/local/share/aclocal/ltversion.m4'
> > > libtoolize: `/usr/local/share/aclocal/ltsugar.m4'
> > > libtoolize: `/usr/local/share/aclocal/lt~obsolete.m4'
> > >
> > > What does this mean?
> > aclocal.m4 is a collection of macros which goes into configure.ac. It
> > includes acinclude.m4 and picks up from /usr/share/aclocal and any -I
> > options passed to aclocal those macros which occurs in configure.ac. I
> > don't know exactly why libtoolize asks you to do this, because it should
> > be done automatically by aclocal, but I think it'll be happy if we
> > declare AC_CONFIG_MACRO_DIR. See the attached patch. libtoolize should
> > now put the m4 files into the m4 subdirectory, but I suggest not to
> > commit them to the repo.
> > We could also tidy the top-level directory by declaring
> > AC_CONFIG_AUX_DIR as in the second patch. Note that the files compile,
> > config.guess, config.sub, install-sh, and missing should then be removed
> > from the top dir and the files in build-aux/ committed instead.
> Complicated regeneration...
> I don't understand - which of two patches should be applied you think (or both, or none)?
The first one will silence libtoolize. I think they're just warnings;
you can check if configure, ltmain.sh and the other files has been
The second patch is completely optional, and helps reduce the noise in
the top-level directory.
More information about the Gc