On Wed June 1 2011, Dr. Stephen Henson wrote: > On Tue, May 31, 2011, gvfb wrote: > > > > > >Thanks, I've got the package for shared libraries libssl0.9.8 as well as > > >the -dev packages which I need to compile IMAP toolkit, I'll probably use > > >those, unless I manage to install from source and then I will enable > > >mod_ssl on apache, with a simple a2enmod. I did config without changing > > >anything on Configure, I simply did config and apparently succesfully, it > > >only informed it was configured for linux - elf. The warnings I got had to > > >do with the pem signatures, I believe, they were sort of: > > > > pem_all.c: In function ???PEM_read_bio_X509_REQ???:pem_all.c:141:1: > > warning: function called through a non-compatible typepem_all.c:141:1: > > note: if this code is reached, the program will abort > > > > (...compiling)pem_all.c:147:1: warning: function called through a > > non-compatible typepem_all.c:147:1: note: if this code is reached, the > > program will abort > > > > (...compiling)pem_x509.c: In function > > ???PEM_read_bio_X509???:pem_x509.c:68:1: warning: function called through a > > non-compatible typepem_x509.c:68:1: note: if this code is reached, the > > program will abortpem_x509.c: In function ???PEM_read_X509???: (same > > result) // this was certainly not the output of the machine, its a comment > > of mine :) > > > > (...compiling)pem_x509.c: In function > > ???PEM_read_bio_X509???:pem_x509.c:68:1: warning: function called through a > > non-compatible typepem_x509.c:68:1: note: if this code is reached, the > > program will abortpem_x509.c: In function ???PEM_read_X509???: (same result) > > > > pem_xaux.c: In function ???PEM_read_bio_X509_AUX???:pem_xaux.c:68:1: > > warning: function called through a non-compatible typepem_xaux.c:68:1: > > note: if this code is reached, the program will abort > > > > (...compiling)pem_pk8.c: In function > > ???PEM_read_bio_PKCS8???:pem_pk8.c:240:1: warning: function called through > > a non-compatible typepem_pk8.c:240:1: note: if this code is reached, the > > program will abort > > > > (...compiling)x_all.c: In function ???d2i_RSA_PUBKEY_bio???:x_all.c:266:9: > > warning: function called through a non-compatible typex_all.c:266:9: note: > > if this code is reached, the program will abort > > > > (Those are not the first 10, but a collection of the warnings of which I > > made a text grouping them by order of appearance and by what I could > > understand they meant, I obviously didn't do a good work there :) > > > > As for the output test (should I do the commands inside those directories > > or is it supposed to be a sort of bash script) Anyway, I'm sorry to say I > > have deleted the directory that I used to build, so I would have to run the > > config and making again. I will let you know if I can manage to do the > > test. > > > > Those relate to the old way OpenSSL (ab)used function pointers which more > recent versions of gcc object to. Although they are "warnings" they will cause > OpenSSL to abort in many places rendering it unusable. You must use a newer > version of OpenSSL sources where this was addressed. >
If for some reason you must stay with the older version of OpenSSL - Your Debian/Ubuntu system supports multiple versions of gcc - You can select v-3.4.? as the default and compile the older OpenSSL with the older version of gcc. Mike > 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 > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
