You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrew Schwartzmeyer (JIRA)" <ji...@apache.org> on 2018/07/17 20:09:00 UTC

[jira] [Commented] (MESOS-3394) Pull in glog 0.3.6 (when it's released)

    [ https://issues.apache.org/jira/browse/MESOS-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547049#comment-16547049 ] 

Andrew Schwartzmeyer commented on MESOS-3394:
---------------------------------------------

Since it's been over a year since the 0.3.5 release, I've [asked|https://github.com/google/glog/issues/345] when we might see a 0.3.6.

> Pull in glog 0.3.6 (when it's released)
> ---------------------------------------
>
>                 Key: MESOS-3394
>                 URL: https://issues.apache.org/jira/browse/MESOS-3394
>             Project: Mesos
>          Issue Type: Task
>          Components: cmake
>            Reporter: Andrew Schwartzmeyer
>            Assignee: Andrew Schwartzmeyer
>            Priority: Major
>              Labels: arm64, build, cmake, freebsd, mesosphere, windows
>
> To build on Windows, we have to build glog on Windows. But, glog doesn't build on Windows, so we had to submit a patch to the project. So, to build on Windows, we download the patched version directly from the pull request that was sent to the glog repository on GitHub.
> When these patches move upstream, we need to change this to point at the "real" glog release instead of the pull request.
> (For details see the `CMakeLists.txt` in `3rdparty/libprocess/3rdparty`.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)