On Apr 2, 2018, at 11:12, Enrico Maria Crisostomo wrote: > Since grpcio includes boringssl sources (an openssl fork), I think the > compiler include files search path is too wide and should not contain > /opt/local/include/openssl. Examining setup.py I haven't been able to tell > why are openssl header files pulled in as well. [snip]
My first question would be: Why does it include boringssl sources, and does it have to use them? Could it use MacPorts openssl instead? If so, that would be my preference.