From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: kaber@trash.net,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: build: resolve autotools suggestions
Date: Tue, 30 Dec 2008 12:27:44 +0100 [thread overview]
Message-ID: <495A05B0.8070700@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0812252021300.17625@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> parent cea9f71f5618250a38acb21c31fbbf93a752f7d4
> commit 6fdeb9468f1bac11698b200530cd454a167e1e39
> Author: Jan Engelhardt <jengelh@medozas.de>
> Date: Thu Dec 25 20:21:36 2008 +0100
>
> build: resolve autotools suggestions
>
> libtool2 wants to put files into m4, so let it have it.
I don't quite understand this change since I'm not a autotools guru. But
according to the manual, there's a more portable way to do this:
"In the future other Autotools will automatically check the contents of
AC_CONFIG_MACRO_DIR, but at the moment it is more portable to add the
macro directory to ACLOCAL_AMFLAGS in Makefile.am, which is where the
tools currently look. If libtoolize doesn't see AC_CONFIG_MACRO_DIR, it
too will honour the first ‘-I’ argument in ACLOCAL_AMFLAGS when choosing
a directory to store libtool configuration macros in. It is perfectly
sensible to use both AC_CONFIG_MACRO_DIR and ACLOCAL_AMFLAGS, as long as
they are kept in synchronisation."
I'd appreciate a more detailed clarification on what you want to do. Thanks.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-30 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 19:21 build: resolve autotools suggestions Jan Engelhardt
2008-12-30 11:27 ` Pablo Neira Ayuso [this message]
2008-12-30 15:18 ` Jan Engelhardt
2009-01-07 14:15 ` Pablo Neira Ayuso
2009-01-07 23:49 ` Jan Engelhardt
2009-01-08 15:55 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=495A05B0.8070700@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.