On Thu January 19 2012, Brooke, Simon wrote: > I'm afraid I've now worked around the problem by using an alternative and > rather less secure solution (i.e. not using openssl at all) - but it's all > inside good firewalls, and the obsolete server will be phased out this year. >
Phasing out the obsolete server is probably the most practical approach. > Issue closed, no solution found :-( > Just getting it to build and link may not have been the end of the problems that would have had to be solved. I think your old system dates from the days of libc-5, not the more recent libc-6. If it does, there are probably more problems lurking that just hadn't been stumbled onto yet. ;-) Mike > -----Original Message----- > From: owner-openssl-us...@openssl.org > [mailto:owner-openssl-us...@openssl.org] On Behalf Of Michael S. Zick > Sent: 18 January 2012 18:00 > To: openssl-users@openssl.org > Subject: Re: Failing to build OpenSSL 1.0.0f on obsolete Debian box (i386, > kernel 2.0.36) > > On Wed January 18 2012, William A. Rowe Jr. wrote: > > On 1/18/2012 9:57 AM, Brooke, Simon wrote: > > > Sadly, removing -fomit-frame-pointer does not work. > > > > Isn't that the default behavior for -O3? > > > > On GCC - yes. > OP is using the ancestor of what is now known as GCC. > > The answer was in another person's post - his binutils > is too old to recognize the assembler instructions used. > > Mike > > > > > > ______________________________________________________________________ > > 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 > > > > Please consider the environment before printing this email. > > > E-mail messages may contain viruses, worms, or other malicious code. By > reading the message and opening any attachments, the recipient accepts full > responsibility for taking protective action against such code. Henry Schein > is not liable for any loss or damage arising from this message. > > The information in this email is confidential and may be legally privileged. > It is intended solely for the addressee(s). Access to this e-mail by anyone > else is unauthorized. > > ______________________________________________________________________ > 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
