The __-prefixed types cannot be assumed to be defined. Use the standard
types instead.

Closes: #6

Aaron Dierking authored Jun 14, 2018 and Guillem Jover committed Jun 18, 2018

Clang's __GNUC__ and __GNUC_MINOR__ definitions are not reliable and may
not be defined at all when targeting the MSVC ABI. Use feature-checking
macros when possible or check for __clang__.

[guillem@hadrons.org: Update for __ protected keyword change. ]
Signed-off-by: Guillem Jover <guillem@hadrons.org>

This should make their usage safer against user macros.

We need this to be able to select different version symbols at
compile-time.

On non-glibc based systems we cannot unconditionally use the
__GLIBC_PREREQ macro as it gets expanded before evaluation. Instead,
if it is undefined, define it to 0.

We should also always declare these functions on non-glibc based
systems. And on systems with a new enough glibc, which provides these
functions, we should still provide the declarations if _GNU_SOURCE
is *not* defined.
Reported-by: Jörg Krause <joerg.krause@embedded.rocks>

Adam Lackorzynski authored Dec 03, 2017 and Guillem Jover committed Jan 13, 2018

Fixes: https://bugs.freedesktop.org/103396

Signed-off-by: Guillem Jover <guillem@hadrons.org>

This is the case on musl.

Fixes: https://bugs.debian.org/810589

Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=99190

Based-on-patch-by: Eric Smith <brouhaha@fedoraproject.org>

Import and adapt from FreeBSD.

Import from FreeBSD.

Glibc tends to include standard headers with special definitions
that make few declarations or macros visible, this stomps over the
overlay #include_next <> logic.
Based-on-patch-by: Robert Millan <rmh@debian.org>

This makes sure the “standard” inclusion protectors are in place, as at
least some FreeBSD kernel headers expect these to be defined to do some
sanity checks.

This affects the pkg-config file now named libbsd-overlay.pc, and the
macro to use the overlay LIBBSD_OVERLAY.

This means that software being ported should not need to be modified in
the usual case, as the libbsd headers will take over the standard
namespace and fill the missing gaps, and include the system headers.

To use this the new libbsd-transparent.pc file can be used through
pkg-config, which should end up doing the right thing.

This way we can replace it later on with a real implementation so that
applications can immediately benefit from it w/o the need to recompile
them.

mirabilos authored Dec 10, 2009 and Guillem Jover committed Dec 10, 2009

This was breaking code actually using those macros.
Signed-off-by: Thorsten Glaser <tg@mirbsd.org>

mirabilos authored Dec 10, 2009 and Guillem Jover committed Dec 10, 2009

Signed-off-by: Thorsten Glaser <tg@mirbsd.org>

This maps more closely the location of the real header. For
transitional purposes keep a <bsd/cdefs.h> that warns and includes
<bsd/sys/cdefs.h>.

Define it to nothing, so that source imported from BSDs can be easily
compiled w/o needing to modify them.

It conflicts with a struct member in a Linux header.