From owner-freebsd-python@FreeBSD.ORG  Fri Feb  4 21:22:25 2011
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 335921065670
	for <freebsd-python@freebsd.org>; Fri,  4 Feb 2011 21:22:25 +0000 (UTC)
	(envelope-from corky1951@comcast.net)
Received: from qmta06.westchester.pa.mail.comcast.net
	(qmta06.westchester.pa.mail.comcast.net [76.96.62.56])
	by mx1.freebsd.org (Postfix) with ESMTP id E68288FC08
	for <freebsd-python@freebsd.org>; Fri,  4 Feb 2011 21:22:24 +0000 (UTC)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60])
	by qmta06.westchester.pa.mail.comcast.net with comcast
	id 3xHj1g0011HzFnQ56xNRZP; Fri, 04 Feb 2011 21:22:25 +0000
Received: from comcast.net ([98.203.142.76])
	by omta14.westchester.pa.mail.comcast.net with comcast
	id 3xNM1g00q1f6R9u3axNNJG; Fri, 04 Feb 2011 21:22:23 +0000
Received: by comcast.net (sSMTP sendmail emulation);
	Fri, 04 Feb 2011 13:22:19 -0800
Date: Fri, 4 Feb 2011 13:22:19 -0800
From: Charlie Kester <corky1951@comcast.net>
To: freebsd-python@freebsd.org
Message-ID: <20110204212219.GE80820@comcast.net>
Mail-Followup-To: freebsd-python@freebsd.org
References: <20110204051500.GA80820@comcast.net>
	<20110204100544.GL78089@deviant.kiev.zoral.com.ua>
	<20110204185512.GB80820@comcast.net>
	<20110204195400.GP78089@deviant.kiev.zoral.com.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20110204195400.GP78089@deviant.kiev.zoral.com.ua>
User-Agent: Mutt/1.4.2.3i
X-Mailer: Mutt 1.4.2.3i
X-Composer: Vim 7.3
Subject: Re: py-numpy build failure,
	multiple definition of `__i686.get_pc_thunk.bx'
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
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: Fri, 04 Feb 2011 21:22:25 -0000

On Fri 04 Feb 2011 at 11:54:00 PST Kostik Belousov wrote:
>On Fri, Feb 04, 2011 at 10:55:12AM -0800, Charlie Kester wrote:
>> On Fri 04 Feb 2011 at 02:05:44 PST Kostik Belousov wrote:
>> 
>> >Can you show the actual invocation of the compiler driver for linking ?
>> 
>> Isn't that the line right before the first report of the error?
>> 
>> cc -shared -pthread -mtune=generic -msse -msse2 -msse3 -mfpmath=sse -O2 
>> -fno-strict-aliasing -pipe -Wl,-rpath=/usr/local/lib/gcc45 
>> build/temp.freebsd-8.2-PRERELEASE-i386-2.7/build/src.freebsd-8.2-PRERELEASE-i386-2.7/numpy/core/src/_sortmodule.o -Lbuild/temp.freebsd-8.2-PRERELEASE-i386-2.7 -lm -o build/lib.freebsd-8.2-PRERELEASE-i386-2.7/numpy/core/_sort.so
>> 
>I wanted the confirmation of exact command that failed. If your
>citation above is right, then port _does not_ use gcc45 to do linkage
>of the module. Generally, crtbegin/crtend.o come from the compiler
>installation, so I am suspicious at least to report of use of
>/usr/lib/crtbegin.So.
>
>Can you enter the port build directory and execute the same command
>manually, substituting "cc" with full path to gcc45 ?

Done.  Replacing "cc" with "gcc45" built the library without any error.
(I didn't need to specify the full path to gcc45.)

So the question is, why is cc being invoked in the first place?  As far
as I know, I'm not doing anything to force using it.  Something seems to
have gone wrong during py-numpy's configtests...