On Sat, Jan 22, 2011, Martin Herrman wrote: > All, > > I am working on a custom firmware for a multimedia device (Eminent > EM7075) which is based on a MIPS EL architecture. > > The official firmware contains a shared libcrypto.so library. > > When I cross-compile for target 'dist' using the 'shared' > configuration option, I still get only a libcrypto.a file (and my > openssl binary is huge compared to the one on the official firmware). > > Now I can not replace the openssl binaries on the official firmware > with a newer version. > > The official firmware uses openssl 0.9.8k, I prefer to use openssl > 1.0.0, but 0.9.8q would also be nice. > > I have also tried to compile 0.9.8k as a shared library, but even in > that case I only get a libcrypto.a. > > After ./Configure it says: > > Configured for dist. > > You gave the option 'shared'. Normally, that would give you shared libraries. > Unfortunately, the OpenSSL configuration doesn't include shared library > support > for this platform yet, so it will pretend you gave the option 'no-shared'. If > you can inform the developpers (openssl-dev\@openssl.org) how to support > shared > libraries on this platform, they will at least look at it and try their best > (but please first make sure you have tried with a current version of OpenSSL). > > How did the manufacturer get a shared libcrypto on the device? >
The "dist" target is really meant only for making distribution tarballs. There are a number of generic Linux platforms you can use which may work for you. Try "linux-generic32" for example (assuming it is a 32 bit system). You can also include the command line option -DL_ENDIAN: some optimisations are used if you specify the endianness of the machine. You can use the auto detect mechanism (./config) by setting up some environment variables as follows: MACHINE: output of uname -m on target system RELEASE: output of uname -r on target system SYSTEM: output of uname -s on target system BUILD: output of uname -v on target system Also you can set CROSS_COMPILE to the cross compiler prefix. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
