From owner-freebsd-python@FreeBSD.ORG Tue Sep 15 12:40:59 2009 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E2191065676; Tue, 15 Sep 2009 12:40:59 +0000 (UTC) (envelope-from miwi@bsdcrew.de) Received: from bsdcrew.de (duro.unixfreunde.de [85.214.90.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4F9A18FC1A; Tue, 15 Sep 2009 12:40:59 +0000 (UTC) Received: by bsdcrew.de (Postfix, from userid 1001) id 5B6D24AF56; Tue, 15 Sep 2009 14:40:57 +0200 (CEST) Date: Tue, 15 Sep 2009 14:40:57 +0200 From: Martin Wilke To: David Southwell Message-ID: <20090915124057.GA69628@bsdcrew.de> References: <200909151105.27983.david@vizion2000.net> <20090915101407.GA58780@bsdcrew.de> <200909151128.17963.david@vizion2000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <200909151128.17963.david@vizion2000.net> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: ports@freebsd.org, python@freebsd.org, beat@FreeBSD.org Subject: Re: ports/138835: Python compile failure X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2009 12:40:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Sep 15, 2009 at 11:28:17AM +0100, David Southwell wrote: > > 1. There has been no blaming only politelly asking question which in the > circumstances seem appropriate. > 2. output of uname -a is included in my reports both ion the PRs and the > reports to freebsd-ports and freebsd-python. > 3. You will see I have already asked James Chang in my posting to ports to > post the output of his uname -a. > 4.dns1# make showconfig > ===> The following configuration options are available for python26-2.6.2_3: > THREADS=on "Enable thread support" > HUGE_STACK_SIZE=off "Use a larger thread stack" > SEM=on "Use POSIX semaphores (experimental)" > PTH=off "Use GNU Pth for threading/multiprocessing" > UCS4=on "Use UCS4 for unicode support" > PYMALLOC=on "Use python's internal malloc" > IPV6=off "Enable IPv6 support" > FPECTL=on "Enable floating point exception handling" > ===> Use 'make config' to modify these settings the problem is here SEM on, if you disable that it builds fine, beat@ has fixed this issus, please test following patch: http://tmp.chruetertee.ch/python26-sem-hack.patch > > > I do not think this is much help as python26-2.6.2_3 will not build > 5. Noone is blaming you - and noone is being aggressive- only asking why the > standard procedure for handling all PR's does not expect maintainers to go > back to the original reporting individual for comments before closing so the > maintainer has the benefit of any additional information that might help to > resolve the problem. When a port freeze is imminent you can however understand > that those who are affected by a failure can feel frustrated when a PR is > closed prematurely. > > David Southwell > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqvi1kACgkQdLJIhLHm/On1DACfRd0XAknn5rrJ4D+tCuOg7PzJ 7McAn25kDQztuaLsP7xUaTCb+bSlz5BM =Tcn8 -----END PGP SIGNATURE-----