From: Pablo Neira Ayuso <pablo@netfilter.org>
To: giorgio.nicole@arcor.de
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] autotools conversion fixups
Date: Wed, 12 Nov 2014 13:01:43 +0100 [thread overview]
Message-ID: <20141112120143.GA32549@salvia> (raw)
In-Reply-To: <1415564772-8873-1-git-send-email-giorgio.nicole@arcor.de>
On Sun, Nov 09, 2014 at 09:26:12PM +0100, giorgio.nicole@arcor.de wrote:
> From: root <root@lord_casco.spaceball>
>
> Add some missing Makefile.am's under the include directory.
>
> Now it is possible to build 'nftables' from a separate build directory
> and produce a release tar archive with a 'make distcheck'.
Thanks. I have merged this update to nftables/autotools branch:
git.netfilter.org/nftables/commit/?h=autotools&id=85035b6c6a1618e7ba726fe6306c804fc1b6c4e8
> diff --git a/autogen.sh b/autogen.sh
> index a62e737..4b6b92d 100755
> --- a/autogen.sh
> +++ b/autogen.sh
> @@ -1,4 +1,11 @@
> #!/bin/bash
>
> -autoreconf -fi;
> +srcdir=`dirname $0`
> +test -z "$srcdir" && srcdir=.
> +
> +ORIGDIR=`pwd`
> +cd $srcdir
> +
> +autoreconf -vfi || exit 1
> rm -Rf autom4te*.cache config.h.in~
> +cd $ORIGDIR || exit $?
The need for this chunk was not justified, I kept this back.
prev parent reply other threads:[~2014-11-12 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 18:25 [PATCH nft 0/5] autotools conversion Pablo Neira Ayuso
2014-11-06 18:25 ` [PATCH nft 1/5] build: use PKG_CHECK_MODULES to check for libmnl and libnftnl Pablo Neira Ayuso
2014-11-06 18:25 ` [PATCH nft 2/5] build: use AC_PROG_YACC and AM_PROG_LEX Pablo Neira Ayuso
2014-11-06 18:25 ` [PATCH nft 3/5] rename parser.y to parser_bison.y Pablo Neira Ayuso
2014-11-06 18:25 ` [PATCH nft 4/5] include: add cli.h Pablo Neira Ayuso
2014-11-06 18:25 ` [PATCH nft 5/5] build: autotools conversion Pablo Neira Ayuso
2014-11-06 20:29 ` Jan Engelhardt
2014-11-07 18:17 ` Giorgio
2014-11-09 20:26 ` [PATCH 1/1] autotools conversion fixups giorgio.nicole
2014-11-12 12:01 ` Pablo Neira Ayuso [this message]
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=20141112120143.GA32549@salvia \
--to=pablo@netfilter.org \
--cc=giorgio.nicole@arcor.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).