netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] build: use _DEFAULT_SOURCE for newer glibc
Date: Thu, 20 Aug 2015 06:49:49 -0400	[thread overview]
Message-ID: <20150820104949.GD21236@vapier> (raw)
In-Reply-To: <alpine.LSU.2.20.1508201011460.28043@nerf40.vanv.qr>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

On 20 Aug 2015 10:12, Jan Engelhardt wrote:
> On Wednesday 2015-08-19 15:08, Mike Frysinger wrote:
> >On 19 Aug 2015 09:09, Jan Engelhardt wrote:
> >> On Wednesday 2015-08-19 00:07, Mike Frysinger wrote:
> >> >Since _BSD_SOURCE is deprecated with newer glibc versions, we get build
> >> >warnings when using only that define.  Add the newer _DEFAULT_SOURCE to
> >> >quiet things down.
> >> 
> >> Why do we even need _BSD_SOURCE/_ISOC99_SOURCE/_DEFAULT_SOURCE? The 
> >> thing apparently builds without it (glibc-2.19), too.
> >
> >i would check with the guy who committed this ;)
> >
> >    build: resolve compile abort in libxt_limit on RHEL5
> >    
> >    libxt_limit.c: In function 'print_rate':
> >        libxt_limit.c:124: error: 'INFINITY' undeclared (first use in
> >        this function)
> 
> Well if that is the case, have you checked that using _DEFAULT_SOURCE
> over _ISOC99_SOURCE+_BSD_SOURCE still works on RHEL5?

i know it won't because _DEFAULT_SOURCE is new to glibc-2.19
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-08-20 10:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 22:07 [PATCH] build: use _DEFAULT_SOURCE for newer glibc Mike Frysinger
2015-08-19  7:09 ` Jan Engelhardt
2015-08-19 13:08   ` Mike Frysinger
2015-08-20  8:12     ` Jan Engelhardt
2015-08-20 10:49       ` Mike Frysinger [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=20150820104949.GD21236@vapier \
    --to=vapier@gentoo.org \
    --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 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).