You are cross-compiling, which means that the platform that you're on cannot actually run the binaries that it builds.
If you do not have any .so files, it may not be able to create shared libraries in that environment. The .a files, in that case, are static libraries. -Kyle H On Sun, Dec 21, 2008 at 2:06 PM, William Estrada <mrumun...@popdial.com> wrote: > Hi group, > > I just built OpenSSL on my FC8 system for my ARM processor. The build > went well but failed the 'make test' with this: > > $ make test > Doing certs > touch rehash.time > testing... > make[1]: Entering directory `/src/ARM/openssl/openssl-0.9.8h/test' > make[2]: Entering directory `/src/ARM/openssl/openssl-0.9.8h' > making all in apps... > make[3]: Entering directory `/src/ARM/openssl/openssl-0.9.8h/apps' > make[3]: Nothing to be done for `all'. > make[3]: Leaving directory `/src/ARM/openssl/openssl-0.9.8h/apps' > make[2]: Leaving directory `/src/ARM/openssl/openssl-0.9.8h' > ../util/shlib_wrap.sh ./destest > ../util/shlib_wrap.sh: line 91: > /src/ARM/openssl/openssl-0.9.8h/test/destest: cannot execute binary file > ../util/shlib_wrap.sh: line 91: > /src/ARM/openssl/openssl-0.9.8h/test/destest: Success > make[1]: *** [test_des] Error 1 > make[1]: Leaving directory `/src/ARM/openssl/openssl-0.9.8h/test' > make: *** [tests] Error 2 > > I also can't find libcrytpo.so, I have libvcrypto.a and libssl.a, but no > *.so files? > Where does the build put them?? > > -- > William Estrada > mrumun...@popdial.com > Mt-Umunhum-Wireless.net ( http://64.124.13.3 ) > Ymessenger: MrUmunhum > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
