On Tue, May 24, 2011 at 6:23 PM, Gordan Bobic <gordan@xxxxxxxxxx> wrote: > On 05/24/2011 03:47 PM, Steev Klimaszewski wrote: > >> mkcd sandbox/openssl (just a little alias/script i have that makes a >> directory with the -p option and then cd's into it) >> sudo apt-get build-dep openssl >> apt-get source openssl (note that we aren't running this with sudo >> because we're planning on building it as a normal user) >> >> This will download the sources to the latest version of openssl that >> is available for whichever version you're on (Maverick is what it >> should be) >> It will extract them, and put them into the directory something like >> openssl-0.whatever > > Ah - this could turn out to be more problematic to do distro-wide than > I'd hoped. Ubuntu 11.04 seems to ship with OpenSSL 0.9.8o. I'm not sure > if the cryptodev support is available in that version. A little > disappointing, really, since 11.04 was released last month and OpenSSL > is way out of date. F13 and RHEL6 both ship with OpenSSL 1.0.0. > > cryptodev driver also fails to complete because the kernel headers are > incomplete (missing mach/memory.h - mach should be a symlink to > arch/arm/mach-mx5/include/mach, but mach-mx5 is empty except for the > build scripts. > > I'd mutter something about teletubby distros, but given this is Fedora > list, I'd probably be preaching to the choir. </rant> ;) > > Gordan > _______________________________________________ > arm mailing list > arm@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/arm > http://packages.ubuntu.com/oneiric/openssl They use openssl 1.0.0 in oneiric, realistically, it should work fine on Maverick, though it may require other dependencies to be upgraded, what I like to do on my personal machines to test, is grab the package, update the changelog and change the oneiric to maverick (very bad of me but meh, I'm just testing it out), and build it. As for the mach, you can checkout the kernel sources, and then symlink it that way. This has been a known bug for ages, and I *think* the only thing we could possibly do to move it around is to generate our own libc6-dev package. -- Steev Klimaszewski <steev@xxxxxxxxxxxxxx> Senior Software Engineer, Genesi USA, Inc. _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
