I've built and tested new gmp-4.3.0-1000 packaging on
both a G4 and G5. In both cases the make test completes
without errors. I did notice that the compatibility level
has been bumped...
Error: Shlibs field says compatibility version for /sw/lib/libgmp.3.dylib is
8.0.0, but it is actually
Jack Howarth wrote:
...I assume it is safe to bump the compatibility level in the
gmp and ppl info files. Unless I am mistaken this issue is also
exactly why the fftw3 package was left at 3.1.2 for so long
since the current 3.2.1 package bumps the compatibility
level but not the soversion.
On Wed, Apr 15, 2009 at 10:34:56AM -0500, Peter O'Gorman wrote:
Jack Howarth wrote:
...I assume it is safe to bump the compatibility level in the
gmp and ppl info files. Unless I am mistaken this issue is also
exactly why the fftw3 package was left at 3.1.2 for so long
since the current
On Apr 15, 2009, at 8:49 AM, Jack Howarth wrote:
So it is completely legal in fink to go ahead and upgrade a package
(gmp-4.3.0, ppl-0.10.1 and fftw3-2.3.1) which has bumped the
compatibility level but not the major soversion number
Yes, completely legal.
as long
as you insure that all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
They are not binary compatible with each other, you can't build against
one and have it work on the other:
diff -Nurd /tmp/nossl.txt /tmp/ssl.txt | c++filt | grep '^+' | wc -l
2029
If you were to build foo against mysql-ssl15-shlibs, it will
