From owner-freebsd-ports@FreeBSD.ORG Mon Feb 28 01:46:17 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A37A106564A for ; Mon, 28 Feb 2011 01:46:17 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id EC4BE8FC14 for ; Mon, 28 Feb 2011 01:46:16 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta05.westchester.pa.mail.comcast.net with comcast id DDlL1g0030bG4ec55DmHES; Mon, 28 Feb 2011 01:46:17 +0000 Received: from comcast.net ([98.203.142.76]) by omta03.westchester.pa.mail.comcast.net with comcast id DDmE1g00G1f6R9u3PDmFja; Mon, 28 Feb 2011 01:46:16 +0000 Received: by comcast.net (sSMTP sendmail emulation); Sun, 27 Feb 2011 17:46:12 -0800 Date: Sun, 27 Feb 2011 17:46:12 -0800 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20110228014612.GA72748@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110225094102.GH21668@droso.net> <4D6AB2E6.1000107@missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4D6AB2E6.1000107@missouri.edu> User-Agent: Mutt/1.4.2.3i X-Mailer: Mutt 1.4.2.3i X-Composer: Vim 7.3 Subject: Re: multiple definition of `__i686.get_pc_thunk.bx' X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2011 01:46:17 -0000 On Sun 27 Feb 2011 at 12:24:06 PST Stephen Montgomery-Smith wrote: >I am the maintainer of the port vis5d+. I just got this email (copied >below) saying that vis5d+ isn't building right now. > >The issue seems to be that some reference to __i686.get_pc_thunk.bx is >included twice at some point. This variable seems to be part of an >object file crtbeginS.o that is created by gcc or gcc45, in what seem to >me to be very mysterious conditions. I am rather sure that the issue >has nothing to do with vis5d+, but rather is something to do with either >gcc45, or libtools, neither of which I understand. > >Does anyone out there have any idea of what the problem is, or how it >can be solved? > I've seen a similar problem with py-numpy. It seems to occur when there's a compiler/linker mismatch. In py-numpy's case, I was able to resolve it by defining LDSHARED to an appropriate value: MAKE_ENV+= LDSHARED="gcc45 -shared" Otherwise, the build was trying to use /usr/local/bin/gcc45 to compiler and /usr/bin/cc to link, resulting in the two different thunk definitions.