From owner-freebsd-python@FreeBSD.ORG Tue Apr 8 08:40:03 2014 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.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 3BCE1808 for ; Tue, 8 Apr 2014 08:40:03 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 29DE9155B for ; Tue, 8 Apr 2014 08:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s388e2Z5018986 for ; Tue, 8 Apr 2014 08:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s388e2N2018985; Tue, 8 Apr 2014 08:40:02 GMT (envelope-from gnats) Date: Tue, 8 Apr 2014 08:40:02 GMT Message-Id: <201404080840.s388e2N2018985@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Rusmir Dusko Subject: Re: ports/188327: math/py-numpy: Numpy is broken X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Rusmir Dusko List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2014 08:40:03 -0000 The following reply was made to PR ports/188327; it has been noted by GNATS. From: Rusmir Dusko To: bug-followup@freebsd.org Cc: "Vladimir Chukharev" Subject: Re: ports/188327: math/py-numpy: Numpy is broken Date: Tue, 8 Apr 2014 10:32:39 +0200 On Tue, 08 Apr 2014 10:11:12 +0300 "Vladimir Chukharev" wrote: > Could you check if the work around from ports/188114 helps in you case? > Try: > > LD_LIBRARY_PATH=/usr/local/lib/gcc47 robocalypto > > You might need to change the version of gcc according to the installed on you computer, > or even find out a correct directory for clang... > Yes this works thanks. This is GCC library PATH issue. -- Best regards, Rusmir Dusko