/libmap.conf
libmap (or symlinking) only works for libraries that have a
compatible ABI.
The version number of libz was bumped precisely because the ABI
changed :)
Install the misc/compat8x port to get libz.so.5 back until you can
replace
diablo-jdk16 with openjdk6.
--
Dan Nelson
java ports, such as diablo-jdk16, are
now installing broken binary files. Even if I put an entry such as
libz.so.4 libz.so.6
in /etc/libmap.conf
libmap (or symlinking) only works for libraries that have a compatible ABI.
The version number of libz was bumped precisely because the ABI
ports, but the binary java ports, such as diablo-jdk16, are
now
installing broken binary files. Even if I put an entry such as
libz.so.4 libz.so.6
in /etc/libmap.conf
libmap (or symlinking) only works for libraries that have a compatible ABI.
The version number of libz was bumped
for libraries that have a compatible
ABI.
The version number of libz was bumped precisely because the ABI changed :)
Install the misc/compat8x port to get libz.so.5 back until you can replace
diablo-jdk16 with openjdk6.
--
Dan Nelson
dnel...@allantgroup.com
Hi,
sorry I tried
such as
libz.so.4 libz.so.6
in /etc/libmap.conf
libmap (or symlinking) only works for libraries that have a compatible
ABI.
The version number of libz was bumped precisely because the ABI changed
:)
Install the misc/compat8x port to get libz.so.5 back until you can
replace
diablo-jdk16
-jdk16,
are now
installing broken binary files. Even if I put an entry such as
libz.so.4 libz.so.6
in /etc/libmap.conf
libmap (or symlinking) only works for libraries that have a compatible
ABI.
The version number of libz was bumped precisely because the ABI changed
:)
Install
.
The version number of libz was bumped precisely because the ABI
changed :)
Install the misc/compat8x port to get libz.so.5 back until you can
replace
diablo-jdk16 with openjdk6.
--
Dan Nelson
dnel...@allantgroup.com
Hi,
sorry I tried to install compat8x but it did not solve
odd, because libz
is pretty 'universal'
Thanks in advanced,
Frank
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
? (I think it rather odd, because
libz is pretty 'universal'
Hi,
Yes, it's true. Only 5.3 and 5.4 are affected. Colin Percival has
confirmed this on the freebsd-security list.
Cheers,
Gábor Kövesdán
___
freebsd-questions@freebsd.org mailing list
the 5.x releases are affected? (I think it rather odd,
because libz is pretty 'universal'
I believe FreeBSD-4.x ships with zlib-1.1.x, whereas the security
problem described above affects only the zlib-1.2.x branch found in
FreeBSD-5, Linux, and elsewhere. I seem to recall Colin Percival
the 5.x releases and not the 4. Is it true
only the 5.x releases are affected? (I think it rather odd, because
libz is pretty 'universal'
Hi,
Yes, it's true. Only 5.3 and 5.4 are affected. Colin Percival has
confirmed this on the freebsd-security list.
Keep in mind, this is already fixed
Hi List,
I've been having problems with ar and nm not being able
to use the library files installed on my system, though
executables created with them seem to work fine.
libz is not the only library this happens with, just using
it as an example.
The output:
ar -t /usr/lib/libz.so.2
/usr/libexec
On Sat, Feb 28, 2004 at 03:29:34AM +, clayton rollins wrote:
Hi List,
I've been having problems with ar and nm not being able
to use the library files installed on my system, though
executables created with them seem to work fine.
libz is not the only library this happens with, just
.
libz is not the only library this happens with, just using
it as an example.
The output:
ar -t /usr/lib/libz.so.2
/usr/libexec/elf/ar: /usr/lib/libz.so.2: File format not recognized
nm /usr/lib/libz.so.2
/usr/libexec/elf/nm: /usr/lib/libz.so.2: no symbols
The problem was first noticed
14 matches
Mail list logo
