From owner-freebsd-python@FreeBSD.ORG  Mon Feb 15 15:20:05 2010
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D76D51065670
	for <freebsd-python@hub.freebsd.org>;
	Mon, 15 Feb 2010 15:20:05 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id AD3C78FC1D
	for <freebsd-python@hub.freebsd.org>;
	Mon, 15 Feb 2010 15:20:05 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o1FFK5kb091198
	for <freebsd-python@freefall.freebsd.org>; Mon, 15 Feb 2010 15:20:05 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1FFK5HH091197;
	Mon, 15 Feb 2010 15:20:05 GMT (envelope-from gnats)
Date: Mon, 15 Feb 2010 15:20:05 GMT
Message-Id: <201002151520.o1FFK5HH091197@freefall.freebsd.org>
To: freebsd-python@FreeBSD.org
From: "b. f." <bf1783@googlemail.com>
Cc: 
Subject: Re: ports/143529: [PATCH] math/py-numpy: does not build
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "b. f." <bf1783@googlemail.com>
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Mon, 15 Feb 2010 15:20:05 -0000

The following reply was made to PR ports/143529; it has been noted by GNATS.

From: "b. f." <bf1783@googlemail.com>
To: "Li-Lun Wang (Leland Wang)" <llwang@infor.org>
Cc: bug-followup@freebsd.org, amdmi3@amdmi3.ru, gerald@freebsd.org
Subject: Re: ports/143529: [PATCH] math/py-numpy: does not build
Date: Mon, 15 Feb 2010 10:11:12 -0500

 On 2/15/10, b. f. <bf1783@googlemail.com> wrote:
 > On 2/15/10, b. f. <bf1783@googlemail.com> wrote:
 >>>From: "Li-Lun Wang (Leland Wang)" <llwang at infor.org>
 >>>To: bug-followup at FreeBSD.org
 >>>Cc:
 >>>Subject: Re: ports/143529: [PATCH] math/py-numpy: does not build
 >>>Date: Mon, 15 Feb 2010 12:50:24 +0800
 >>>
 >>> -----BEGIN PGP SIGNED MESSAGE-----
 >>> Hash: SHA1
 >>
 >>>The following patch will fix the problem.  It first detects if
 >>> binutils>=2.18.50 is installed.  If it is, then it patches numpy so
 >>> that the new fenv.h will be used if __FreeBSD_version <= 900009.
 >>
 >> This fixes the build problem on i386 (although we're stuck with
 >> possible run-time problems when numpy is built with the newer binutils
 >> until the latest fenv.h changes are backported to all supported
 >> versions of FreeBSD), but this code is machine-dependent, and fenv.h
 >> needs to be selected based on ARCH.
 
 Oops: it seems that the r203441 only affected amd64 and i386, so the
 latest headers shouldn't be used for the other architectures (there
 may be problems lurking there, too, but that's another matter).  So my
 sketch should be altered to something like:
 
 
 ...
 .if exists(${LOCALBASE}/bin/as) && ${OSVERSION} <= 900009 && \
 (${ARCH} == "i386" || ${ARCH} == "amd64")
 .if ${ARCH} == "i386"
  FP_ARCH= i387
 .elif ${ARCH} == "amd64"
  FP_ARCH= ${ARCH}
 .endif
 MASTER_SITES+= http://svn.freebsd.org/base/head/lib/msun/%SUBDIR%/:fp
 MASTER_SITE_SUBDIR+= ${FP_ARCH}/:fp
  DISTFILES+= fenv.h:fp
 .endif
 .endif
  ...
   pre-configure:
 .if exists(${LOCALBASE}/bin/as) && ${OSVERSION} <= 900009
       ${CP} ${DISTDIR}/fenv.h
  ${WRKSRC}/numpy/core/include/numpy/fenv/fenv.h; \
       ${PATCH} ${PATCH_DIST_ARGS} < ${FILESDIR}/fenv.patch; \
 .endif
 ...
 
 But again, this probably isn't necessary if lang/gcc44 is only using
 the base system binutils, and indeed may fail if lang/gcc44 was built
 when devel/binutils was not installed -- so we should see first what
 action will be taken regarding lang/gcc44, or use a more refined test.
 
 b.