From owner-freebsd-python@FreeBSD.ORG Fri Sep 5 14:21:20 2014 Return-Path: Delivered-To: freebsd-python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F407375C for ; Fri, 5 Sep 2014 14:21:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DAD231ADD for ; Fri, 5 Sep 2014 14:21:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s85ELJ2m078743 for ; Fri, 5 Sep 2014 14:21:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-python@FreeBSD.org Subject: [Bug 192365] x11-toolkits/py-wxPython30 build fails Date: Fri, 05 Sep 2014 14:21:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jilles@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-python@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 14:21:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192365 --- Comment #6 from Jilles Tjoelker --- 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.