All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nftables: improve build system
Date: Mon, 13 Jan 2014 09:56:46 +0000	[thread overview]
Message-ID: <20140113095646.GC15457@macbook.localnet> (raw)
In-Reply-To: <alpine.LSU.2.11.1401131035120.16954@nerf08.vanv.qr>

On Mon, Jan 13, 2014 at 10:47:24AM +0100, Jan Engelhardt wrote:
> 
> On Monday 2014-01-13 10:12, Patrick McHardy wrote:
> >
> >>       build: remove unused checks
> >
> >Why aren't we instead evaluating the results?
> 
> I don't know - I did not write those lines in the first place. A
> reasonable hypothesis is that this is just old boilerplate copied
> from somewhere else rather than actually looking for what the
> commands executed by make really need.

That was not my question. I asked why we're not evaluating *instead* of
removing them.

> Furthermore, like a lot of NF software, it is tied to Linux where the
> existence of arpa/inet.h, fcntl.h, malloc(3), and so on is
> pretty much guaranteed.
> 
> The only point to check for absence of stdint.h is when at the same
> time, the code provides alternative ways to get what it needs (like a
> hand-crafted typedef unsigned char uint8_t) - which are not present
> either. So checking for stdint.h is rather useless.
> 
> >>       build: rename conflicting parser.h instances
> >
> >The changelog mentions something about -I but no further explanation about
> >why this change is done and the effects.
> 
> How so? Commit says:
> 
> 	If -I. is on the command line …
> 
> and -I. is on the command line with autoconf (more precisely,
> -I${srcdir} -I${builddir} -I${path_to_config_h} is).
> 
> 	… #include <parser.h> becomes (=matches) ./parser.h
> 	instead of ../include/parser.h.
> 
> Basically you never ever want to have a header with the same include
> path. Even #include <regex.h> is prone to ambiguity if you had
> -I/usr/include/boost (which you should not of course, but people
> do all kinds of weird things sometimes), suddenly matching
> /usr/include/boost/regex.h instead of /usr/include/regex.h.
> 
> It's all about distributions, and it takes a regular packager to know.

Jan, the changelog simply needs a description what is wrong, why it
is wrong and what is changed. You can't expect people to know what
parameters autoconf uses on the command line and I guess you know that.
--
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

  reply	other threads:[~2014-01-13  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  9:07 nftables: improve build system Jan Engelhardt
2014-01-13  9:07 ` [PATCH 1/3] build: remove unused checks Jan Engelhardt
2014-01-13  9:07 ` [PATCH 2/3] build: rename conflicting parser.h instances Jan Engelhardt
2014-01-13  9:07 ` [PATCH 3/3] build: use automake and pkgconfig Jan Engelhardt
2014-01-13  9:12 ` nftables: improve build system Patrick McHardy
2014-01-13  9:47   ` Jan Engelhardt
2014-01-13  9:56     ` Patrick McHardy [this message]
2014-01-13 10:56       ` Jan Engelhardt

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=20140113095646.GC15457@macbook.localnet \
    --to=kaber@trash.net \
    --cc=jengelh@inai.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.