From: mkl@pengutronix.de (Marc Kleine-Budde)
Subject: [lttng-dev] [PATCH] urcu: fix deprecation warning with new glibc
Date: Mon, 1 Jun 2015 17:16:27 +0200 [thread overview]
Message-ID: <556C774B.8090206@pengutronix.de> (raw)
In-Reply-To: <1237864258.1418.1433168737082.JavaMail.zimbra@efficios.com>
On 06/01/2015 04:25 PM, Mathieu Desnoyers wrote:
> ----- On Jun 1, 2015, at 3:16 PM, Marc Kleine-Budde mkl at pengutronix.de wrote:
>
>> This patch fixes the following warning:
>>
>> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE
>> are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>> # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>
> And why does this patch just add _DEFAULT_SOURCE without removing _BSD_SOURCE ?
> Is it the intended transition path ? Is it documented somewhere ?
From http://man7.org/linux/man-pages/man7/feature_test_macros.7.html:
_BSD_SOURCE (deprecated since glibc 2.20)
[...]
Since glibc 2.20, this macro is deprecated. It now has the
same effect as defining _DEFAULT_SOURCE, but generates a com?
pile-time warning (unless _DEFAULT_SOURCE is also defined).
Use _DEFAULT_SOURCE instead. To allow code that requires
_BSD_SOURCE in glibc 2.19 and earlier and _DEFAULT_SOURCE in
glibc 2.20 and later to compile without warnings, define both
_BSD_SOURCE and _DEFAULT_SOURCE.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150601/f0968ea9/attachment.sig>
next prev parent reply other threads:[~2015-06-01 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 13:16 Marc Kleine-Budde
2015-06-01 14:25 ` Mathieu Desnoyers
2015-06-01 15:16 ` Marc Kleine-Budde [this message]
2015-06-01 15:25 ` Mathieu Desnoyers
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=556C774B.8090206@pengutronix.de \
--to=mkl@pengutronix.de \
/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