On Tue, Feb 8, 2011 at 8:42 PM, Jan Steffens <jan.steff...@gmail.com> wrote: > Hello, > > I help maintain the Arch Linux multilib repository and was wondering how > OpenSSL should be built on a x86_64 multilib system. My approach so far has > been this: > > export CC="gcc -m32" > export CXX="g++ -m32" > export PKG_CONFIG_PATH="/usr/lib32/pkgconfig" > ./Configure linux-elf --prefix=/usr --openssldir=/etc/ssl \ > --libdir=lib32 shared zlib enable-md2 -Wa,--noexecstack > > make > > A user is getting crashes in Picasa that are fixed by replacing the OpenSSL > libraries in lib32 with their versions from the Arch Linux i686 distribution. > So I believe were doing something wrong when building OpenSSL for multilib. > See https://bugs.archlinux.org/task/21248 . > > Also, a opensslconf.h is generated that's different from the 64-bit build. > Do you have an opinion on how to handle this? I wanted to rename the different > headers into opensslconf-64.h and opensslconf-32.h and create a opensslconf.h > that includes the right one based on wordsize. > > So far we weren't aware of the header problem (We simply used the 64-bit > headers), and I believe this could have been the cause of a crash in 32-bit > wine, see https://bugs.archlinux.org/task/22045 . However, testing with the > above method didn't fix the crashing. Still, I believe it would be the correct > thing to do. > > The entire buildscript we are using for lib32-openssl is available at > http://projects.archlinux.org/svntogit/community.git/tree/lib32-openssl/trunk/
Can I please have some input on this? ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org