|
From: Anders F B. <af...@us...> - 2014-01-14 22:51:45
|
Thomas Leonard wrote: >>> I've built new binaries (2.6-rc3) against upstream openssl and >>> libcurl, so hopefully untainted by Debian or Fedora craziness. Anyway, >>> the symbol versions seem to be gone :-) >> >> Hmm, this still doesn't work for me: >> >> $ 0install run --not-before=2.6-rc3 http://0install.net/tools/0install.xml >> /home/tim/.cache/0install.net/implementations/sha256new_XBH32RLRWOXKRBDE7RA4L357CHREDW4FHU6BMZWB3F465S3RQQOA/files/0install: >> error while loading shared libraries: libcrypto.so.1.0.0: cannot open >> shared object file: No such file or directory >> >> ldd still reports: >> >> libcrypto.so.1.0.0 => not found >> libssl.so.1.0.0 => not found >> >> If you've built against the upstream libssl, doesn't that mean you >> need to depend on upstream-named .so files as well? > > Yes. It's not a complete solution, but it does > > a) make it possible to run on Fedora (with the symlink hack) > b) get rid of the warning on Arch > > Since nothing depends on the OCaml feed currently, I think we can > still release this as 2.6. Distributions can include it and build > their own binaries. Then we can try to figure out some dynamic linker > tricks to make the binaries generic for 2.7 (or static link openssl, > though I'd prefer to avoid that). I think there are some licensing issues when mixing GPL and OpenSSL, since the licenses aren't compatible - but there is an exception with the "system" openssl, which means the dynamically linked one. Including any funky naming schemes, like "1.1.0e" or "10" or so... So I think we need to build RPMS*, should also fix RHEL6's glibc-2.12 ? I uploaded a 2.6-rc3 binary for OS X ("darwin") now, as well as the two for GNU ("linux") already there. It requires glib/gtk+ and gnupg, but fortunately both openssl and libcurl are provided by the system. The rest can be added by just installing my PyGTK.pkg and GnuPG.pkg. Upgraded to OCaml 4.01.0 and OPAM 1.1.0 first, before building it... --anders * Both EPEL 6 and Fedora 20 are currently shipping 0install-2.3.3 as "zeroinstall-injector". We need a new .spec, for 0install-2.6! |