Date: Wed, 25 Jul 2018 22:36:25 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230046] [exp-run] Make timespecadd(3) and friends public Message-ID: <bug-230046-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230046 Bug ID: 230046 Summary: [exp-run] Make timespecadd(3) and friends public Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: asomers@FreeBSD.org CC: ports-bugs@FreeBSD.org Created attachment 195458 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D195458&action= =3Dedit bring our timespecadd etc definitions in line with NetBSD's The timespecadd(3) family of macros were imported from NetBSD back in r3502= 9. However, they were initially guarded by #ifdef _KERNEL. In the meantime, we have grown at least 28 syscalls that use timespecs in some way, leading many programs both inside and outside of the base system to redefine those macro= s. It's better just to make the definitions public. Our kernel's definitions of timespecadd and timespecsub are slightly differ= ent than NetBSD's and OpenBSD's. This revision changes our definition to match theirs. This change could cause ports breakage if a port: 1) includes <sys/time.h>,=20 2) locally defines timespecadd or a related macro, and 3) doesn't guard that definition with #ifndef timespecadd --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230046-7788>