Hi, New version of PyPy just got released, and seeing that the binaries do not depend on (incompatible with Slackware) libffi anymore, I decided to repackage them instead of building from source (which takes lots of time and RAM).
I tested pypy with some code of mine, it worked great except one thing:
whenever I invoke pypy executable, I get the following warnings in
stderr:
./pypy: /lib/libssl.so.0.9.8: no version information available
(required by ./pypy)
./pypy: /lib/libcrypto.so.0.9.8: no version information available
(required by ./pypy)
Running ldd -v ./pypy shows:
libssl.so.0.9.8 => /lib/libssl.so.0.9.8 (0xf76cd000)
libcrypto.so.0.9.8 => /lib/libcrypto.so.0.9.8 (0xf7587000)
and in version information section:
libssl.so.0.9.8 (OPENSSL_0.9.8) => not found
libcrypto.so.0.9.8 (OPENSSL_0.9.8) => not found
I recalled reading a discussion on some mailing list (can't find a link
to archives though) where it was explained that this is what happens
when you use something built against OpenSSL from Debian on a different
system. Wanting to be sure, I checked Debian source package for openssl
and indeed found a patch where they add
$shared_ldflag .= " -Wl,--version-script=openssl.ld";
line to Configure script and create openssl.ld file containing
OPENSSL_0.9.8 {
global:
*;
};
So, I am quite confident that PyPy was built using Debian (or
derivative) system.
Now, the real questions: is it safe to use such binary on Slackware? If
yes, is it possible to suppress these warnings?
--
Audrius Kažukauskas
pgpmcbpi4krvU.pgp
Description: PGP signature
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
