From owner-freebsd-python@FreeBSD.ORG Sun Feb 1 23:36:46 2015 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A59EF3AF for ; Sun, 1 Feb 2015 23:36:46 +0000 (UTC) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7726F671 for ; Sun, 1 Feb 2015 23:36:46 +0000 (UTC) Received: by mail-oi0-f48.google.com with SMTP id v63so41944583oia.7 for ; Sun, 01 Feb 2015 15:36:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=y1FEPMPoWe4YZvdQKb1NcXn4h1NHp99nMpORrNaCUBQ=; b=Cl1ihbRCLulAWRfQxdoO8jrx0hYO71iHZbLCEzW+pj+uD4UfVEg85sAb5F4hKF616W 4eyuV5o/rTUL6bPH9HNFZy2fwsEO1UK2ZhN4SNzGnUKOocpkOfoxokVsPz3hrxTdHYA3 ilxycN6J5o+HgAdycv5dn3qorRsOjiLtFEMhAdXlZGeXtoOnXJJZa/ObzojvNiy5nHkD KjTV9gZCLzsXyXaIj4jyjxLmuxYDNnTNBvh9shEGm8GacS69sCodjOV6KK6tktvlg6B8 yfNn7WhR8PScbGtpZVTbbCSwIqVwxHjiwGp4Md1mleO/WojCjEMQstD/fEH/Dk2i+8lg cM0w== X-Received: by 10.202.232.65 with SMTP id f62mr9876072oih.116.1422833805551; Sun, 01 Feb 2015 15:36:45 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id a6sm8837056obx.15.2015.02.01.15.36.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Feb 2015 15:36:44 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 2 Feb 2015 00:36:41 +0100 From: Baptiste Daroussin To: python@FreeBSD.org Subject: Python's configure misunderstand freebsd Message-ID: <20150201233641.GH11558@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hAW+M2+FUO+onfmf" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Sevan Janiyan X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 23:36:46 -0000 --hAW+M2+FUO+onfmf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, At FOSDEM I have been reported by Sevan (CCed) that the python's configure scripts thinks it is forbidden to have a lib named libpython2.so.X.Y on FreeBSD which is wrong. Here is a patch that fixes it on python2 unfortunatly as a result that means everything linked to libpython2.so.1 will need a bump. (same thing should be done for other pythons) I would prefer that you guys decides when how and so on to make that change happening. https://people.freebsd.org/~bapt/respect-the-libname-decided-by-upstream.diff I modified the configure script and not the configure.ac because the patch is not worth have to depend on autotools to regenerate the configure. That should also be upstreamed (if one of you could do it it would be great :)) Best regards, Bapt --hAW+M2+FUO+onfmf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTOuIkACgkQ8kTtMUmk6EwihgCghnspACA2yLBEUTjrwsSelQpZ XmsAnijlm3YsPTLhmGUMT19QGvAafn4T =N/82 -----END PGP SIGNATURE----- --hAW+M2+FUO+onfmf--