Date: Mon, 28 Feb 2011 10:29:12 +0200 From: Andriy Gapon <avg@freebsd.org> To: Stephen Montgomery-Smith <stephen@missouri.edu> Cc: autotools@freebsd.org, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: multiple definition of `__i686.get_pc_thunk.bx' Message-ID: <4D6B5CD8.7090507@freebsd.org> In-Reply-To: <4D6AD327.3040302@missouri.edu> References: <20110225094102.GH21668@droso.net> <4D6AB2E6.1000107@missouri.edu> <4D6AD327.3040302@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/02/2011 00:41 Stephen Montgomery-Smith said the following: > 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 problem seems to be with libtool. If I run a command like: > > libtool -mode=link g++45 stuff stuff > > then libtool does NOT use g++45, but it uses c++ instead. If I hand edit > /usr/local/bin/libtool and replace c++ by g++45, this fixes the problem I > describe below. It looks like libtool (foolishly?) records whatever CC/CXX is set when libtool itself is built. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D6B5CD8.7090507>