freebsd stable - Jul 2017 - Compile-time check for clock_nanosleep()

Hi!
>   Some time ago, I ported a linux program that was using clock_nanosleep().
> I see now that the extra code I'd put in isn't needed anymore in
11-stable,
> as it appears this call was added in 11.1.  My question is, to
> properly protect these changes, what is the best way to know at
> compile time, either (a) that that call is in libc, or (b) that
> I'm compiling on FreeBSD 11.1 or later ?
Use __FreeBSD_version from sys/param.h:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/versions.html

-- 
pi at opsec.eu            +49 171 3101372                         3 years to go
!

> On Jul 3, 2017, at 14:46, Kurt Jaeger <lists at opsec.eu> wrote:
> 
> Use __FreeBSD_version from sys/param.h:
> 
>
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/versions.html
  Thanks.  That looks great.  Also, for my specific case of the addition of
clock_nanosleep(), it looks from time.h like I could use "__POSIX_VISIBLE
>= 200112?.  Maybe that isn?t safe, since later looking at time.h on 11.0 and
on 11.1, the latter has a definition for clock_nanosleep() in that block, but
the former does not.

  Yeah, digging around it appears that stable/11/sys/sys/param.h at r316498 had
__FreeBSD_version at 1100512, and it was raised to 1100513 in revision 318197. 
And, clock_nanosleep was MFC?d into 11-stable in-between the two, at revision
317618.  So, not a precise match there, but >= 1100513 should be safe.

  Thanks!

                                      - Chris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170703/bb7d86c3/attachment.sig>