New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build 7.56.0 fails on CentOS 5.11 i686 and x64 #1955

Closed
javyer opened this Issue Oct 6, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@javyer

javyer commented Oct 6, 2017

I did this

./configure --enable-shared=yes --with-ssl
make
...
CC vtls/libcurl_la-openssl.lo
vtls/openssl.c: In function ‘cert_stuff’:
vtls/openssl.c:845: error: implicit declaration of function ‘EVP_PKEY_id’
make[2]: *** [vtls/libcurl_la-openssl.lo] Error 1
make[2]: Leaving directory /tmp/curl-7.56.0/lib' make[1]: *** [all] Error 2 make[1]: Leaving directory/tmp/curl-7.56.0/lib'
make: *** [all-recursive] Error 1

I expected the following

build without errors

curl/libcurl version

curl 7.56.0, Released on the 4th of October 2017.
curl-7.56.0.tar.gz

[curl -V output]
N/A

operating system

CentOS release 5.11 (Final)
OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
rpm openssl-devel-0.9.8e-40.el5_11 & openssl-0.9.8e-40.el5_11 (official)
gcc --version
gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-55)
Copyright (C) 2006 Free Software Foundation, Inc.

@bagder

This comment has been minimized.

Show comment
Hide comment
@bagder

bagder Oct 6, 2017

Member

Please let me know how/if the #1956 fix works for you!

Member

bagder commented Oct 6, 2017

Please let me know how/if the #1956 fix works for you!

@javyer

This comment has been minimized.

Show comment
Hide comment
@javyer

javyer Oct 6, 2017

Thanks Bagder, it builds ;-)

javyer commented Oct 6, 2017

Thanks Bagder, it builds ;-)

@javyer javyer closed this Oct 6, 2017

bagder added a commit that referenced this issue Oct 6, 2017

openssl: fix build without HAVE_OPAQUE_EVP_PKEY
Reported-by: Javier Sixto
Fixes #1955
Closes #1956

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.