[Nut-upsdev] AC_CONFIG_MACRO_DIR

Arnaud Quette aquette.dev at gmail.com
Mon Dec 29 19:17:18 UTC 2008


2008/12/29 Charles Lepple <clepple at gmail.com>

> On Mon, Dec 29, 2008 at 10:24 AM, Arjen de Korte <nut+devel at de-korte.org<nut%2Bdevel at de-korte.org>>
> wrote:
> > Charles,
> >
> > When running autoreconf in the trunk, I get a couple of additional files
> > since I upgraded to openSUSE 11.1. Most likely, this is due to a newer
> > version of the auto(whatever) tools that are used. Or I never looked at
> this
> > more closely before.
> >
> > libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> > libtoolize: copying file `m4/libtool.m4'
> > libtoolize: copying file `m4/ltoptions.m4'
> > libtoolize: copying file `m4/ltsugar.m4'
> > libtoolize: copying file `m4/ltversion.m4'
> > libtoolize: copying file `m4/lt~obsolete.m4'
> >
> > Should we do something with this? I Googled for the AC_CONFIG_MACRO_DIR
> > macro and it seems like we could/should add this to configure.in.
>
> It looks like AC_CONFIG_MACRO_DIR defaults to m4, so I don't know if
> we want to explicitly set that.
>

I've added that one since autoreconf was complaining...


> Or are you thinking that we should have a separate directory for m4
> files that we don't provide? Not quite sure how that would work.
>
> > Since I'm
> > no expert on this, is there someone who knows? Otherwise it is probably
> > better to svn:ignore these.
>
> Peter Selinger was our resident expert who did the conversion to
> automake (from plain autoconf). I'd agree that we can just add them to
> svn:ignore until we know more about them.
>

yup, fine ATM since these are regenerated at autoreconf, so before making a
dist...

-- Arnaud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20081229/1a56f5db/attachment.htm 


More information about the Nut-upsdev mailing list