[Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

[Michal Klocek]

Hi

I am sorry to say that but your build environment looks broken.
Returning -I/opt/local/include for glib-2.0 (if this is true) is bogus
and it will include newer openssl headers, since there are in
/opt/local/include/openssl, (according to your build log). It looks like
sth is misconfigured for pkg-config. Please note pkg-cofig always strips
out system paths (expect you explicitly set PKG_CONFIG_ALLOW_SYSTEM_CFLAGS
/ PKG_CONFIG_ALLOW_SYSTEM_LIBS).

Br

Michal

On 12/22/2017 01:45 PM, René J. V. Bertin wrote:
> Michal Klocek wrote:
> 
>> might want to check what actually returns -I/opt/local/include/glib-2.0
>> -I/opt/local/lib/glib-2.0/include -I/opt/local/include.  A good starting
>> point might be glib-2.0.pc file (or simply run pkg-config  --cflags
>> glib-2.0)
> 
> Yeah, that'd be the culprit, or a culprit.
> 
> Question is what to do about that, other than making sure no conflicting headers 
> exist wherever they shouldn't be, during the build.
> 
> It also doesn't tell us why the openssl headers from /usr/include/openssl do NOT 
> cause the same problem as the newer ones in /opt/local/include/openssl . I don't 
> see any options to exclude the usual system include directories.
> 
> R.
> 
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>