mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bannier (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MESOS-7581) Specifying an unbundled dependency can cause build to pick up wrong Boost version
Date Mon, 29 May 2017 08:35:04 GMT
Benjamin Bannier created MESOS-7581:
---------------------------------------

             Summary: Specifying an unbundled dependency can cause build to pick up wrong
Boost version
                 Key: MESOS-7581
                 URL: https://issues.apache.org/jira/browse/MESOS-7581
             Project: Mesos
          Issue Type: Bug
          Components: build
    Affects Versions: 1.2.2, 1.3.1, 1.1.3
            Reporter: Benjamin Bannier
            Assignee: Benjamin Bannier


Specifying an unbundled dependency can cause the build to pick up a wrong Boost version. Assuming
we have e.g., both protobuf and Boost installed in {{PREFIX}}, configuring with {{--with-protobuf=PREFIX}}
causes the build to pick up the Boost version from {{PREFIX}} instead of using the bundled
one.

This appears to be due to how we specify Boost include paths. Boost paths are added with {{-isystem}}
to suppress warnings; the protobuf include path, on the other hand, would be added with {{-I}}.
GCC and for compatibility clang first search all paths specified with {{-I}} left-to-right
before looking at paths given with {{-isystem}}, see [the GCC documenation|https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html].



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message