Lukas Vacek added the comment:
Thanks for the explanation of the secret workings behind the scenes.
What a productive and polite response.
--
___
Python tracker
<https://bugs.python.org/issue38
Lukas Vacek added the comment:
For the record, this would have been solved more than a year ago already.
When this change was proposed more than a year ago it was rejected with "There
is no need to add more configure flags to build Python with a custom OpenSSL
installation. " ye
Lukas Vacek added the comment:
Christian, I don't want to argue.
Feel free to close both this bug and the PR as "enhancement rejected". Adding
one ./configure option is not really worth arguing over, I can always compile
python as I need. I just tried to solve the same pro
Lukas Vacek added the comment:
In ideal world OpenSSL would provide stable ABI just like the other libraries
Python depends on. That would be, unarguably, the best way to achieve that
goal. Agreed.
Aferall frequent OpenSSL ABI breakages are the reason why apple switched to
their own
Lukas Vacek added the comment:
However, I'm still convinced many would appreciate adding this ./configure
option:
https://github.com/pyenv/pyenv/issues/1184#issuecomment-403149437
https://joshspicer.com/python37-ssl-issue
https://superuser.com/questions/1428109/install-python-3-7-3
Lukas Vacek added the comment:
Fair enough.
Btw. I picked versions 3.7 and up to show this feature should eventually be
backported to older CPython versions that depend on OpenSSL >= 1.0.2.
This feature is to avoid relying on rpath and relying on a seperate
installation to be installed
Change by Lukas Vacek :
--
title: Setup: support linking openssl staticly -> Setup: support linking
openssl statically
___
Python tracker
<https://bugs.python.org/issu
Change by Lukas Vacek :
--
keywords: +patch
pull_requests: +16663
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17153
___
Python tracker
<https://bugs.python.org/issu
New submission from Lukas Vacek :
Since 3.7 python depends on OpenSSL>=1.0.2 - this makes it hard to compile
Python with SSL on older (yet still vendor supported) linux distributions.
It's easy to compile CPython even on old distributions like RHEL5, RHEL6,
Ubuntu14.04 etc. except
Lukas Vacek added the comment:
Actually CFLAGS do indeed come before any include directories.
I can reproduce your problem:
mkdir /tmp/extra_include
cp /usr/include/expat.h /usr/include/expat_external.h /tmp/extra_include/
make CFLAGS="-I/tmp/extra_include"
You should use CPPFLAGS
Lukas Vacek added the comment:
Hi Peter,
Thanks for taking the time to report your issue. I just tried on fresh
up-to-date CentOS 6 and I could not reproduce the issue.
However, I think I figured out what went wrong. I can see you are supplying
custom -I and -L paths (-I/apps/prod/releases
New submission from Lukas Vacek:
Hey,
Currently when a module builds successfully during cpython build but it can't
be imported (import check around line 330 in setup.py) the module shows in
"Failed to build these modules: " which can be misleading.
Especially when linking ag
Lukas Vacek added the comment:
attaching patch
--
keywords: +patch
nosy: +Lukas.Vacek
Added file: http://bugs.python.org/file33905/fix_expat_names.patch
___
Python tracker
<http://bugs.python.org/issue19
13 matches
Mail list logo