I guess the build machine had ssl installed and Python hence picked up the dependency. We should uninstall openssl-devel on the build machines or make it clear that openssl is a dependency for the binary package. Since the distro vendor is distributing openssl in this case there is no doubt that the system library clause is in effect.
On Saturday, November 24, 2012 8:24:42 PM UTC, Kazimierz Kurz wrote: > > I download Sage 5.4.1 precompiled binary release. > During first run sage starts with updating paths process, and then > suddenly throws at me Error: *"ERROR:root:code for hash md5 was not > found."* > > Whilst there are some information in trac about this, it is related to > process of build from the source, not installation of binaries. > > So, if You have the same problem - just run *first* ( just after > unpacking of the binaries, within directory where You place Your new sage > release) > > *./sage -i openssl* > > It downloads and compile openssl into local sage/local/lib directory, and > then run ./sage as described in manual. And it works! > > My system Ubuntu 10.04.4 LTS > Openssl was installed from repositories, and present in /lib directory. I > do not know why sage 5.4.1 does not seen it. > > Best Regards > Kazek Kurz > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To post to this group, send email to sage-support@googlegroups.com. To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support?hl=en.
