From owner-freebsd-python@FreeBSD.ORG Sat Feb 5 03:03:11 2011 Return-Path: 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 AED2E106566B for ; Sat, 5 Feb 2011 03:03:11 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C2378FC14 for ; Sat, 5 Feb 2011 03:03:11 +0000 (UTC) Received: by gxk8 with SMTP id 8so1214919gxk.13 for ; Fri, 04 Feb 2011 19:03:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:date:message-id:subject :from:to:cc:content-type; bh=1lNSX7mRITIqgfPwr+88dA2+yl6RuYWRcTLyUeYAFyo=; b=GQKWFS4F13ojhDp70iOzg1YC9R6LefaWQFurR3TJZ73DFysm7cnPm7OJLwQ6wrb/Bw Js7Nzb1QUaLsLp8yGBC1u687wqZnHI9GBfYWXxsOZnzrCKdF1wv2Q0FV4MjLRp+4TY0Y YIiu1i9xEfwp6AoaYug5GlTbGBmwQhFHKkzF0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; b=ANXT9yADZ8P/nsi1QgDFyaxgPljIubb+DRWX/9sv/ogh/lyPmCGAgRcuLBpWtJKyGv TLla1A0bMr2nzx5Cn0gceS9ESezQavFxZb569oG804owW/AMqtSBxkajJxIqjAhbE6Re JXQuWpK6fnZFhWAZmrGWGQozQRsaIa3XE4U54= MIME-Version: 1.0 Received: by 10.236.95.17 with SMTP id o17mr2145035yhf.10.1296874226819; Fri, 04 Feb 2011 18:50:26 -0800 (PST) Received: by 10.236.105.197 with HTTP; Fri, 4 Feb 2011 18:50:26 -0800 (PST) Date: Fri, 4 Feb 2011 21:50:26 -0500 Message-ID: From: "b. f." To: Charlie Kester Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-python@FreeBSD.org 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 Reply-To: bf1783@gmail.com List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2011 03:03:11 -0000 > 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... By default, this port and some of its prerequisites are built with lang/gcc45 and devel/binutils, because they USE_FORTRAN, while other prerequisites are built with the older (and not completely compatible) base system compiler and base system toolchain. This has led to problems in the past, and they have not all been solved. So you should be alert when dealing with this port and any dependent ports, and make sure that they are using gcc45, /usr/local/bin/ld, etc., rather than their older base system counterparts, which may be cached in different files, e.g., /usr/local/lib/python*/config/Makefile, /usr/local/lib/python*/site-packages/numpy/distutils/site.cfg, or /usr/local/lib/python*/site-packages/numpy/distutils/system_info.py. Also, the ports should link with the appropriate LDFLAGS directing them to the newer shared libraries in /usr/local/lib/gcc45, rather than the older libraries in /usr/lib. b.