"Horowitz, Michael" wrote: > > Hello, > > When I build OpenSSL with shared libraries the programs that link against > them don't work.
> > That all worked without any problems or errors. The config script > configured for "solaris-sparcv9-gcc". > > When building other programs such as wget, lynx, pine, apache-ssl, and a > random program(that doesn't use ssl) and trying to compile them with ssl > either with a "--with-ssl" option for wget and lynx, the apache-ssl patch > for apache, and simply compiling with "-lssl" with the random program, the > programs either failed to build or produced an binary that couldn't be > executed. > > For example, with wget, the configure script produced this message: > "checking whether SSL libs are resolved at runtime... no". > With lynx and apache, a random program that was built to use to generate > some header files during make, failed because it could not execute the > binary. Removing the "-lssl" from the compiler options and building those > programs produces a working executable. Pine built fine, but had the same > problems as the other files in the lynx and apache build. > > Here is what happens when I run pine built with ssl linked in: > ./pine > bash: ./pine: cannot execute binary file > > Here is what ldd says: > ldd pine > ldd: pine: execution failed pine: Exec format error > > This same exact thing happens with any program linked with the shared > versions of the openssl libraries. The static ones seem to work fine. > > Can anyone help me get the shared libraries to work? Try taking out the UltraSparc option. Use ./Configure shared solaris-sparcv8-gcc See if this works for openssl. Bruce Forsberg ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
