Closed Sjoerdjanssenen closed 8 years ago
Same here
I have this too. Related: https://github.com/pyca/cryptography/issues/2750
Same.
Same issue here on 3.16.0-46-generic #62~14.04.1-Ubuntu. This happened while trying to build OpenSSL (1.0.2g-1+deb.sury.org~trusty+1).
creating build/temp.linux-x86_64-2.7/build
creating build/temp.linux-x86_64-2.7/build/temp.linux-x86_64-2.7
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c build/temp.linux-x86_64-2.7/_openssl.c -o build/temp.linux-x86_64-2.7/build/temp.linux-x86_64-2.7/_openssl.o
build/temp.linux-x86_64-2.7/_openssl.c:710:6: error: conflicting types for ‘BIO_new_mem_buf’
BIO *BIO_new_mem_buf(void *, int);
^
In file included from /usr/include/openssl/asn1.h:65:0,
from build/temp.linux-x86_64-2.7/_openssl.c:426:
/usr/include/openssl/bio.h:692:6: note: previous declaration of ‘BIO_new_mem_buf’ was here
BIO *BIO_new_mem_buf(const void *buf, int len);
^
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
Thank you for posting your solution of downgrading, @singlow. Your solution worked for me. Those of you who are still looking for a temporary solution, check this out.
Can you try upgrading to a newer version of pip and seeing if the problem goes away? I suspect 1.5.4 is causing the unicode error (and then the C build error is a separate thing).
All of you tracking this issue might also (and more easily) try setting the env var LC_ALL=C
while running letsencrypt-auto and see if that helps while we work on a better fix:
LC_ALL=C letsencrypt-auto ...
I'm going to assume this is a pip error until somebody shows it still happens under the latest pip (in which case please reopen). We're working around it in https://github.com/letsencrypt/letsencrypt/issues/2596.
I just got this error on Laravel Forge. Thought I should paste it here.