From: Patrick McHardy <kaber@trash.net>
To: giorgio.nicole@arcor.de
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Re: [PATCH 4/7] autotools conversion: include the header 'config.h' in every C source file.
Date: Thu, 10 Jul 2014 14:52:46 +0200 [thread overview]
Message-ID: <20140710125245.GA10007@macbook.localnet> (raw)
In-Reply-To: <1421640070.472816.1404988338916.JavaMail.ngmail@webmail23.arcor-online.net>
On Thu, Jul 10, 2014 at 12:32:18PM +0200, giorgio.nicole@arcor.de wrote:
>
>
>
> ----- Original Nachricht ----
> Von: Patrick McHardy <kaber@trash.net>
> An: Giorgio Dal Molin <giorgio.nicole@arcor.de>
> Datum: 10.07.2014 12:04
> Betreff: Re: [PATCH 4/7] autotools conversion: include the header 'config.h'
> in every C source file.
>
> > On Mon, Jul 07, 2014 at 04:19:28PM +0200, Giorgio Dal Molin wrote:
> > > Added an #include <config.h> to all the C source files so that the
> > results
> > > of the tests in the configure script are available to all the compilation
> > > units.
> > >
> > > We could have added the include also to 'yacc_parser.y' and 'scanner.l'
> > > but we don't, because it is not strictly needed and to avoid to define
> > > the variable 'VERSION' two times.
> >
> > > --- a/src/cli.c
> > > +++ b/src/cli.c
> > > @@ -11,6 +11,9 @@
> > > *
> > > * Development of this code funded by Astaro AG (http://www.astaro.com/)
> > > */
> > > +#ifdef HAVE_CONFIG_H
> > > +#include <config.h>
> > > +#endif
> >
> > Do we really need those ifdefs?
> >
>
> Hi,
>
> do you mean just the #ifdefs or the whole #include <config.h> ?
>
> The config.h should be included, unless there are real problems with it; one I've found
> is the preprocessor variable VERSION defined in the yacc source 'src/yacc_parser.y':
> it would conflict with the same variable defined in the 'config.h'.
>
> Actually, if you just build the package under linux, using the ./configure... && make all install
> you will always generate / include the config.h, so the #ifdef is not strictly needed.
So let's remove them. Also I think a lot of programs are using CFLAGS to
-include config.h, that might be easier.
Please change this one way or the other and address Pablo's comment and I'll
merge this.
next prev parent reply other threads:[~2014-07-10 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 10:32 Aw: Re: [PATCH 4/7] autotools conversion: include the header 'config.h' in every C source file giorgio.nicole
2014-07-10 12:52 ` Patrick McHardy [this message]
2014-07-10 13:57 ` Aw: " giorgio.nicole
2014-07-10 14:08 ` [PATCH] " Giorgio Dal Molin
2014-07-10 14:54 ` Pablo Neira Ayuso
2014-07-12 9:09 ` 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=20140710125245.GA10007@macbook.localnet \
--to=kaber@trash.net \
--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 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.