You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:33 UTC
[jira] [Issue Comment Deleted] (MESOS-9240) CSI protobuf build
fails when dependency tracking is disabled.
[ https://issues.apache.org/jira/browse/MESOS-9240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated MESOS-9240:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> CSI protobuf build fails when dependency tracking is disabled.
> --------------------------------------------------------------
>
> Key: MESOS-9240
> URL: https://issues.apache.org/jira/browse/MESOS-9240
> Project: Mesos
> Issue Type: Bug
> Components: build
> Reporter: James Peach
> Assignee: James Peach
> Priority: Major
> Fix For: 1.8.0
>
>
> Generating the CSI protobufs depends on the "$(builddir)/include/csi" directory being created as configuration time. This only happens when automate build dependencies are enabled, however. By default, rpmbuild will pass {{\--disable-dependency-tracking}}, which will prevent this directory being created, and the build will fail like so:
> {noformat}
> ./../include/mesos/v1/master/master.proto
> /usr/bin/protoc -I../../include -I../../src -I../3rdparty/csi-0.2.0 --cpp_out=../include ../../include/mesos/v1/quota/quota.proto
> /usr/bin/protoc -I../../include -I../../src -I../3rdparty/csi-0.2.0 --cpp_out=../include ../../include/mesos/v1/resource_provider/resource_provider.proto
> ../include/csi/: No such file or directory
> /usr/bin/protoc -I../../include -I../../src -I../3rdparty/csi-0.2.0 --cpp_out=../include ../../include/mesos/v1/scheduler/scheduler.proto
> /usr/bin/protoc -I../../include -I../../src -I../3rdparty/csi-0.2.0 --cpp_out=. ../../src/master/registry.proto
> make[2]: *** [../include/csi/csi.grpc.pb.cc] Error 1
> make[2]: *** Waiting for unfinished jobs....
> ../include/csi/: No such file or directory
> make[2]: *** [../include/csi/csi.pb.cc] Error 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)