From owner-freebsd-ports@FreeBSD.ORG Sat Jan 4 23:06:48 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A642549 for ; Sat, 4 Jan 2014 23:06:48 +0000 (UTC) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 984EA1926 for ; Sat, 4 Jan 2014 23:06:46 +0000 (UTC) Received: from server.rulingia.com (c220-239-250-249.belrs5.nsw.optusnet.com.au [220.239.250.249]) by vps.rulingia.com (8.14.7/8.14.7) with ESMTP id s04N6hvP059414 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Jan 2014 10:06:44 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.7/8.14.7) with ESMTP id s04N6ckV073292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 5 Jan 2014 10:06:38 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.7/8.14.7/Submit) id s04N6bGO073291; Sun, 5 Jan 2014 10:06:37 +1100 (EST) (envelope-from peter) Date: Sun, 5 Jan 2014 10:06:37 +1100 From: Peter Jeremy To: Torbjorn Granlund Subject: Re: Advice about /usr/ports/math/gmp Message-ID: <20140104230637.GB72376@server.rulingia.com> References: <86d2k9uhw1.fsf@shell.gmplib.org> <9D1C0F6F-0683-430D-AB96-3E29693B3163@FreeBSD.org> <868uuwrek7.fsf@shell.gmplib.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <868uuwrek7.fsf@shell.gmplib.org> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.22 (2013-10-16) Cc: FreeBSD Mailing List X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2014 23:06:48 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2014-Jan-03 17:53:02 +0100, Torbjorn Granlund wrote: >We have been forced to add three FreeBSD-related items to the releases >notes: Your use of "work" in the following notes is ambiguous. Are you referring to building gmp, another program linking against gmp or executing a program that links against gmp? > * This release will not work on FreeBSD/amd64 7.x, 8.x or 9 series > before 9.3 with a Haswell CPU or any other CPU which supports the > BMI2 instructions. The reason is that the FreeBSD m4 command is not > correctly implemented. (Workaround: Use an older GMP release, or > install GNU m4 from /usr/ports and tell GMP to use it.) Does gmp use m4 other than during the build process? Using GNU m4 to build gmp is a relatively painless workaround. > * This release will not work on FreeBSD/amd64 before version 10 using > the 32-bit ABI. The reason is broken limits.h and broken dynamic > linking. (Workaround: Use an older GMP release if using the 32-bit > ABI on these FreeBSD releases is important.) Again, what exactly do you mean? Building code using the 32-bit ABI on FreeBSD/amd64 was not supported prior to FreeBSD 10 so it was only a lucky fluke if it previously worked. If you mean that a 32-bit program using gmp (ie one compiled on FreeBSD/i386) will not run on FreeBSD/amd64, please provide more details (ie the PR number). > * This release will not work on FreeBSD/amd64 10.0 using the 32-bit > ABI. The reason is bugs in the compiler 'clang'. (Workaround: > Compiling gcc from /usr/ports might work, except that gcc depends on > GMP; we have not been able to test that workaround since > FreeBSD/i386 10.0 does not work for us under KVM or Xen.) Please clarify what you mean by "work" here. Since FreeBSD 10.0 is the first release where building i386 executables is supported, it is quite likely there are bugs in this area. Can you please provide more details (ie the PR numbers) on the problems you encountered with 32-bit gmp 5.2 on FreeBSD/amd64 10.0 as well as the problems you encountered using FreeBSD/i386 10 on KVM and Xen. On 2014-Jan-03 21:33:12 +0100, Torbjorn Granlund wrote: >This is not the right place for FreeBSD bug reports, and I did not >indend to do so. Agreed. It _is_ expected that you would include references to the bug reports though. > I was only trying to ease the maintenence of >/usr/ports/math/gmp. Except that by providing vague and incomplete references to problems, you aren't doing anything to ease the ports maintenance. From the information you provided, it's impossible to determine if the port should have GNU m4 as a build and/or run dependency. >I have reported two of these problems. (I have not reported the >remaining two problems, and I do not intend to do that. Sorry. Again, >I feel that I would abuse thios mailing list by discussing that here.) So, what you're saying is that gmp 5.2 has problems on FreeBSD but you aren't going to provide any details that would assist us to resolve them. This just wastes everyone's time. --=20 Peter Jeremy --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iKYEARECAGYFAlLIk/1fFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDBCRjc3QTcyNTg5NEVCRTY0RjREN0VFRUZF OEE0N0JGRjAwRkI4ODcACgkQ/opHv/APuIcRAACeNoGudHzQoT0gkbpaK7Db4zki /TwAnjHHbsPmNOshslLnJB/AteSMIwd7 =66Fi -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5--