clang vs gcc: installing python-qpid-proton

2017-07-28 Thread Hamza Sheikh
I need to install python-qpid-proton in a Python virtualenv with pip. The behavior is different when using gcc to install it versus using clang. With clang the proton library does not build as it can't find openssl/ssl.h. It builds if DYLD_LIBRARY_PATH=/opt/local/lib is exported. After a successfu

Re: clang vs gcc: installing python-qpid-proton

2017-07-28 Thread Ryan Schmidt
It's news to me that MacPorts gcc has /opt/local/include in its default search path, and my first response is that I would not want it to do that, especially if as you say MacPorts clang doesn't do the same thing. So I would consider this a bug in MacPorts gcc that I would want to fix. Does anyo

Re: clang vs gcc: installing python-qpid-proton

2017-07-28 Thread Hamza Sheikh
On Fri, Jul 28, 2017 at 12:10 PM, Ryan Schmidt wrote: > The usual way to get a compiler to find MacPorts software is to supply > -isystem/opt/local/include in CPPFLAGS and -L/opt/local/lib in LDFLAGS. > Different build systems may have different requirements. I'm not familiar > with how pip doe