From owner-freebsd-python@FreeBSD.ORG Tue Jul 22 01:46:34 2014
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id E7FBDA5B
for <freebsd-python@FreeBSD.org>; Tue, 22 Jul 2014 01:46:34 +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 CDAF42AAF
for <freebsd-python@FreeBSD.org>; Tue, 22 Jul 2014 01:46:34 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6M1kYqF020595
for <freebsd-python@FreeBSD.org>; Tue, 22 Jul 2014 01:46:34 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-python@FreeBSD.org
Subject: [Bug 191991] www/chromium fails configure steps
Date: Tue, 22 Jul 2014 01:46:34 +0000
X-Bugzilla-Reason: CC
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 Only Me
X-Bugzilla-Who: koobs@FreeBSD.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: chromium@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-191991-17421-zfoEOFsjLg@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191991-17421@https.bugs.freebsd.org/bugzilla/>
References: <bug-191991-17421@https.bugs.freebsd.org/bugzilla/>
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
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
<mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
<mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2014 01:46:35 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191991
Kubilay Kocak <koobs@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |koobs@FreeBSD.org
--- Comment #6 from Kubilay Kocak <koobs@FreeBSD.org> ---
Carlos is correct, the SEM option was made the default in r361735 [1] for the
following reasons:
- POSIX semaphores are now supported and working in all supported FreeBSD
(GENERIC) releases.
- They are expected and part of a default upstream Python build (unless not
supported by the system, or broken)
- While 'technically' optional in that one *can* disable them with the
appropriate configure argument, it is not exposed in ./configure --help or
otherwise documented as a user-configurable knob.
- To address issues just like this for binary packages (see special note in
commit log below)
[1] https://svnweb.freebsd.org/ports?view=revision&revision=361735
--
You are receiving this mail because:
You are on the CC list for the bug.