Date: Fri, 05 Sep 2014 14:21:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-python@FreeBSD.org Subject: [Bug 192365] x11-toolkits/py-wxPython30 build fails Message-ID: <bug-192365-17421-sVVSgX9G0C@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192365-17421@https.bugs.freebsd.org/bugzilla/> References: <bug-192365-17421@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192365 --- Comment #6 from Jilles Tjoelker <jilles@FreeBSD.org> --- It looks like this port is trying to customize the visibility of things in headers in an unsupported way, by requesting a standard-compliant environment (such as by defining _POSIX_SOURCE, _POSIX_C_SOURCE or _XOPEN_SOURCE) and manually defining __BSD_VISIBLE in addition to that. Because functions like wcscasecmp() and strnlen() were only added in POSIX.1-2008, they are not exposed if a strict POSIX.1-2001 environment is requested. The effect of a manual __BSD_VISIBLE on this is undefined, and is in practice likely to change when a formerly non-standard extension becomes standard. For most applications, the default environment is appropriate. It shows everything except a few things like getline(), which can be enabled with specific defines. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192365-17421-sVVSgX9G0C>