this seems to make the most sense for bulk builds to me.
Should any other platforms fail, we can make a note of it
and exclude them along with Darwin.
Also, add two distribution patches from upstream:
[2008-11-09]
When calling mpf_set_str (perhaps indirectly via
mpf_init_set_str or mpf_inp_str, or via the C++ interface) with the
argument for the base set to 0, any exponent will be ignored.
[2008-11-08]
The mpf_eq function sometimes compares too few bits, not
just too many (the latter is documented).
This might lead to precision loss. When the experimental
--enable-nails feature is enabled at the same time --enable-cxx is
enabled, make check fails. This failure is actually due to bugs
in tests/cxx/t-prec.cc, which makes it use mpf_eq incorrectly.
This patch makes mpf_eq compare the right number of bits,
neither too few, nor to many.
The patch also fixes the test case, and documentation.
(not strictly necessary, but I figured I'd keep in line with
their recommendations)
PKGREVISION++
Changes between GMP version 4.2.3 and 4.2.4
Bugs:
* Fix bug with parsing exponent '+' sign in mpf.
* Fix an allocation bug in mpf_set_str, also affecting mpf_init_set_str, and
mpf_inp_str.
Speedups:
* None, except that proper processor recognition helps affected processors.
Features:
* Recognize new AMD processors.
Changes between GMP version 4.2.2 and 4.2.3:
Bugs:
* Fix x86 CPU recognition code to properly identify recent AMD and Intel
64-bit processors.
* The >> operator of the C++ wrapper gmpxx.h now does floor rounding, not
truncation.
* Inline semantics now follow the C99 standard, and works with recent GCC
releases.
* C++ bitwise logical operations work for more types.
* For C++, gmp.h now includes cstdio, improving compiler compatibility.
* Bases > 36 now work properly in mpf_set_str.
Speedups:
* None, except that proper processor recognition helps affected processors.
Features:
* The allocation functions now detect overflow of the mpz_t type. This means
that overflow will now cause an abort, except when the allocation
computation itself overflows. (Such overflow can probably only happen in
powering functions; we will detect powering overflow in the future.)
When using mpf_set_str, mpf_init_set_str, or mpf_inp_str
with a base > 36, the supplied base will actually be ignored,
and the exponent 0 will be supplanted. [2007-12-10]
All tests pass on NetBSD/amd64 4.99.58.
Bump revision.
to build a "fat" binary on (${MACHINE_ARCH} == "i386" && ${OPSYS} != "Darwin").
This isn't enabled by default now, but it might be useful for build builds,
as it uses cpuid at runtime to choose the most appropriate assembler code.
Insofar as I can tell, no BUILDLINK_A[BP]I_DEPENDS bump is necessary.
NOTE: Support for Darwin-*-i386 and Darwin-*-x86_64 has been improved,
see below. Thus, I recommend that we test building the assembler code
on Darwin at some point.
Changes between GMP version 4.2.1 and 4.2.2:
* License is now LGPL version 3.
Bugs:
* Shared library numbers corrected for libcxx.
* Fixed serious bug in gmpxx.h where a=a+b*c would generate garbage.
Note that this only affects C++ programs.
* Fix crash in mpz_set_d for arguments with large negative exponent.
* Fix 32-bit ABI bug with Itanium assembly for popcount and hamdist.
* Fix assembly syntax problem for powerpc-ibm-aix with AIX
native assembler.
* Fix problems with x86 --enable-fat, where the compiler where told to
generate code for the build machine, not plain i386 code as it should.
* Improved recognition of powerpc systems wrt Altivec/VMX capability.
* Misc minor fixes, mainly workarounds for compiler/assembler bugs.
Speedups:
* "Core 2" and Pentium 4 processors, running in 64-bit mode will get a
slight boost as they are now specifically recognized.
Features:
* New support for x86_64-solaris
* New, rudimentary support for x86-apple-darwin and x86_64-apple-darwin.
(Please see http://gmplib.org/macos.html for more information.)
Changes between GMP version 4.2 and 4.2.1
Bugs:
* Shared library numbers corrected.
* Broken support for 32-bit AIX fixed.
* Misc minor fixes.
Speedups:
* Exact division (mpz_divexact) now falls back to plain division for large
operands.
Features:
* Support for some new systems.
Changes between GMP version 4.1.4 and 4.2
Bugs:
* Minor bug fixes and code generalizations.
* Expanded and improved test suite.
Speedups:
* Many minor optimizations, too many to mention here.
* Division now always subquadratic.
* Computation of n-factorial much faster.
* Added basic x86-64 assembly code.
* Floating-point output is now subquadratic for all bases.
* FFT multiply code now about 25% faster.
* Toom3 multiply code faster.
Features:
* Much improved configure.
* Workarounds for many more compiler bugs.
* Temporary allocations are now made on the stack only if small.
* New systems supported: HPPA-2.0 gcc, IA-64 HP-UX, PowerPC-64 Darwin,
Sparc64 GNU/Linux.
* New i386 fat binaries, selecting optimised code at runtime (--enable-fat).
* New build option: --enable-profiling=instrument.
* New memory function: mp_get_memory_functions.
* New Mersenne Twister random numbers: gmp_randinit_mt, also now used for
gmp_randinit_default.
* New random functions: gmp_randinit_set, gmp_urandomb_ui, gmp_urandomm_ui.
* New integer functions: mpz_combit, mpz_rootrem.
* gmp_printf etc new type "M" for mp_limb_t.
* gmp_scanf and friends now accept C99 hex floats.
* Numeric input and output can now be in bases up to 62.
* Comparisons mpz_cmp_d, mpz_cmpabs_d, mpf_cmp_d recognise infinities.
* Conversions mpz_get_d, mpq_get_d, mpf_get_d truncate towards zero,
previously their behaviour was unspecified.
* Fixes for overflow issues with operands >= 2^31 bits.
Caveats:
* mpfr is gone, and will from now on be released only separately. Please see
www.mpfr.org.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
* Bug fix to FFT multiplication code (crash for huge operands).
* Bug fix to mpf_sub (miscomputation).
* Support for powerpc64-gnu-linux.
* Better support for AMD64 in 32-bit mode.
* Upwardly binary compatible with 4.1.3, 4.1.2, 4.1.1, 4.1, 4.0.1, 4.0,
and 3.x versions.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
