Details
Description
Stout doesn't build in a standalone configuration:
$ cd ~/src/mesos/3rdparty/stout $ ./bootstrap $ cd ~/build/stout $ ~/src/mesos/3rdparty/stout/configure ... $ make ... make[1]: Leaving directory '/home/vagrant/build/stout/3rdparty' make[1]: Entering directory '/home/vagrant/build/stout/3rdparty' make[1]: *** No rule to make target 'googlemock-build-stamp'. Stop. make[1]: Leaving directory '/home/vagrant/build/stout/3rdparty' make: *** [Makefile:1902: 3rdparty/googletest-release-1.8.0/googlemock-build-stamp] Error 2
Note that the build expects 3rdparty/googletest-release-1.8.0/googlemock-build-stamp, but googletest hasn't been staged yet:
[vagrant@fedora-26 stout]$ ls -l 3rdparty/ total 44 drwxr-xr-x. 3 vagrant vagrant 4096 Jan 18 2016 boost-1.53.0 -rw-rw-r--. 1 vagrant vagrant 0 Jul 5 06:16 boost-1.53.0-stamp drwxrwxr-x. 8 vagrant vagrant 4096 Aug 15 2016 elfio-3.2 -rw-rw-r--. 1 vagrant vagrant 0 Jul 5 06:16 elfio-3.2-stamp drwxr-xr-x. 10 vagrant vagrant 4096 Jul 5 06:16 glog-0.3.3 -rw-rw-r--. 1 vagrant vagrant 0 Jul 5 06:16 glog-0.3.3-build-stamp -rw-rw-r--. 1 vagrant vagrant 0 Jul 5 06:16 glog-0.3.3-stamp -rw-rw-r--. 1 vagrant vagrant 734 Jul 5 06:03 gmock_sources.cc -rw-rw-r--. 1 vagrant vagrant 25657 Jul 5 06:03 Makefile
Attachments
Issue Links
- is related to
-
MESOS-7364 Upgrade vendored GMock / GTest
- Resolved