<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - g++ 5.4.0 cannot compile poppler (due to C++11 option)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97915#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - g++ 5.4.0 cannot compile poppler (due to C++11 option)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97915">bug 97915</a>
from <span class="vcard"><a class="email" href="mailto:trueroad@trueroad.jp" title="Masamichi Hosoda <trueroad@trueroad.jp>"> <span class="fn">Masamichi Hosoda</span></a>
</span></b>
<pre>(In reply to Adrian Johnson from <a href="show_bug.cgi?id=97915#c4">comment #4</a>)
<span class="quote">> I got gfile.cc to compile on cygwin by adding #define _BSD_SOURCE to the
> file. Although I read somewhere that _BSD_SOURCE has been replaced by
> _DEFAULT_SOURCE. We may need to add something to configure.ac and cmake to
> set the feature macro based on the compiler version.
>
> The problem with using -std-gnu++11 is we don't want to allow gnu features
> that are incompatible with Visual C++.</span >
I've found the description of _BSD_SOURCE and _DEFAULT_VERSION.
<a href="http://man7.org/linux/man-pages/man7/feature_test_macros.7.html">http://man7.org/linux/man-pages/man7/feature_test_macros.7.html</a>
It says:
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>