> On 2 Apr 2018, at 19:50, Joshua Root wrote:
>
> On 2018-4-3 02:12 , Enrico Maria Crisostomo wrote:
>> How is the compiler include file search path set up in this case? The
>> /opt/local/include/openssl path should come from MacPorts, but I don't know
>> where it's set and how I can override
> On 3 Apr 2018, at 00:34, Ryan Schmidt wrote:
>
>
> 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. E
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 open
On 2018-4-3 02:12 , Enrico Maria Crisostomo wrote:
> How is the compiler include file search path set up in this case? The
> /opt/local/include/openssl path should come from MacPorts, but I don't know
> where it's set and how I can override it.
It's not: src/boringssl/err_data.c says #include .