You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2022/01/07 16:57:00 UTC
[jira] [Comment Edited] (TEZ-4300) Download protoc automatically compile/development time
[ https://issues.apache.org/jira/browse/TEZ-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470460#comment-17470460 ]
László Bodor edited comment on TEZ-4300 at 1/7/22, 4:56 PM:
------------------------------------------------------------
[~mgrigorov]: is there a protobuf release that actually used in case of ARM64?
https://github.com/protocolbuffers/protobuf/releases/
or if you have it installed and you can point an environment variable to the protoc executable, it's also fine after TEZ-4300:
{code}
export PROTOC_PATH=/path/to/protoc # where protoc is manually installed
mvn clean install -DskipTests -Dprotobuf.version=3.x.y
{code}
was (Author: abstractdog):
[~mgrigorov]: is there a protobuf release that actually used in case of ARM64?
https://github.com/protocolbuffers/protobuf/releases/
or if you have it installed and you can point an environment variable to the protoc executable, it's also fine after TEZ-4300:
{code}
export PROTOC_PATH=/path/to/protoc
mvn clean install -DskipTests -Dprotobuf.version=3.x.y
{code}
> Download protoc automatically compile/development time
> ------------------------------------------------------
>
> Key: TEZ-4300
> URL: https://issues.apache.org/jira/browse/TEZ-4300
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Attachments: tez_build_protobuf_3_7_1.log
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently, Tez cannot be built out of the box because tez-api needs a protobuf compiler (protoc executable), which was also a problematic dependency in a sense that downloading/installing it is a burden on developers. Even if we have tons of [gists|https://gist.github.com/abstractdog/1eddeac9cc09815ded5253e3a83293a8] for that, it's still uncomfortable. Not to mention if we want to support more versions at the same time.
> Shipping the typically used versions (2.5.0, 3.x for later) of the protoc executable could make sense, but I'm not sure at the moment if it has any license issues, [need to check|https://github.com/protocolbuffers/protobuf/blob/master/LICENSE], also it's not general, instead an intelligent script could do it for developers.
> For 2.5, it should be done from source: https://github.com/protocolbuffers/protobuf/releases/tag/v2.5.0
> But for newer versions, the protoc executable can be downloaded from the releases page: https://github.com/protocolbuffers/protobuf/releases/tag/v3.7.1
> https://github.com/protocolbuffers/protobuf/releases/download/v3.7.1/protoc-3.7.1-osx-x86_64.zip
> https://github.com/protocolbuffers/protobuf/releases/download/v3.7.1/protoc-3.7.1-linux-x86_64.zip
--
This message was sent by Atlassian Jira
(v8.20.1#820001)