All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: IPT [PATCH] yay, autotools!
Date: Wed, 28 Nov 2007 09:48:53 +0100	[thread overview]
Message-ID: <474D2B75.9070301@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711280140320.4181@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> 	"The Reason For Holding Off 1.4.0"
> 
> Converts the iptables build infrastructure to autotools.

Oh joy :)

> Many important changes. Should read INSTALL as a start.
> 
> 	- iptables-static will be a multi binary. I doubt you want split
> 	binaries on embedded anyway (diskspace constraints).
> 
> 	- A new binary, iptables-mtss is built (semi-static, with glibc but
> 	without plugins).
> 
> 	I do not think iptables-static makes any sense (neither now nor
> 	before this move to autotools), because ld rightly tells me that
> 	building with -static will cause loading of glibc parts /anyway/
> 	because of getserv*() in xt_dccp and so on.

Well, the reason for linking statically is IMO not to be able to run
without a libc but to avoid having tons of shared object files.

> 
> 	- Can build both (full, semi-)static and dynamic at the same time
> 
> 	- not so happy with .*-test yet, but I really wanted to get rid of
> 	the fixed module list in extensions/Makefile because it's just a
> 	.rej PITA.


We only have two .test files left, and frankly I think the concept
sucks, if you look at the lists you'll find plenty of reports of
people missing extensions because their distribution built against
an old kernel. Thats why I included the headers and moved to
unconditional building for every single extension that is or has
been supported by mainline kernel.

> 	- any reason not to always build ipv6 unconditionally?

I can't think of one.
> 
> 	- I think we should move all manuals to libxt_*.man or perhaps
> 	even *.man, would reduce Makefile LOC.

You mean for the ones where we have an IPv4 and IPv6 version, but
no xtables extension? I'm not sure they're all similar ...

> Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
> 
> Patch instructions:
>  delete Makefile
>  delete extensions/Makefile
>  delete libiptc/Makefile
>  create autogen.sh with mode 0755
>  rename libipt_dscp_helper.c to dscp_helper.c (delete hunks before applying)


In general, I don't have an opinion on this patch other that
I think all the autotool stuff is way to complicated. Your
patch looks reasonable simple, so I'm not objecting, but I'd
like to hear some arguments what this is buying us. I assume
the changes above could also be achieved with some simple
changes to the existing Makefile.

  parent reply	other threads:[~2007-11-28  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  0:43 IPT [PATCH] yay, autotools! Jan Engelhardt
2007-11-28  1:21 ` Philip Craig
2007-11-28  8:48 ` Patrick McHardy [this message]
2007-11-28 11:09   ` Jan Engelhardt
2007-11-28 11:25     ` Patrick McHardy
2007-11-28 11:48       ` Jan Engelhardt
2007-11-28 11:58         ` Patrick McHardy
2007-11-28 12:05           ` Jan Engelhardt
2007-11-28 13:11             ` IPT [PATCH] autotools, number 2 Jan Engelhardt
2007-11-28 16:22         ` IPT [PATCH] yay, autotools! Laszlo Attila Toth
2007-11-29  7:48       ` Jozsef Kadlecsik

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=474D2B75.9070301@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@computergmbh.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 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.