[
https://issues.apache.org/jira/browse/KUDU-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153800#comment-17153800
]
ASF subversion and git services commented on KUDU-3159:
-------------------------------------------------------
Commit 59ea81869643f7c41e73133344f7a04ce6d5c08e in kudu's branch
refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=59ea818 ]
[docs][docker] KUDU-3159 Fix missing devtoolset3 package on el6
devtoolset3 package is no longer available on software collections causing
build failures when building kudu from source on RHEL/CentOS 6.
Using one of the only available unofficial copr repositories to install
devtoolset3 since devtoolset3 is EOL already and we plan to migrate to a newer
compiler version and hence a newer devtoolset for RHEL/CentOS 6 soon.
Separate JIRA KUDU-3160 tracks upgrading devtoolset version for el6.
Tests:
- Successfully ran kudu-unit tests using devtoolset3 downloaded from the repo
on an internal cloudera test job.
- Verified doc instructions using ascii doc plugin in CLion IDE
- Partially verified build with docker BASES=centos:6 docker/docker-build.sh
on Mac OS 10.15.4
Verified from console that devtoolset3 repo was installed.
However ran into issue while building kudu-python from what looks
like an unrelated issue due to failure to find kudu_client library.
Change-Id: I9c4b9546c835df26f993ed6164e92f2d4c55c3fe
Reviewed-on: http://gerrit.cloudera.org:8080/16114
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke <[email protected]>
> Fix installation instructions for devtoolset3 for RHEL/CentOS6
> --------------------------------------------------------------
>
> Key: KUDU-3159
> URL: https://issues.apache.org/jira/browse/KUDU-3159
> Project: Kudu
> Issue Type: Bug
> Components: build, docker, documentation
> Reporter: Bankim Bhavsar
> Assignee: Bankim Bhavsar
> Priority: Major
>
> devtoolset3 package is no longer available on software collections causing
> build failures when building kudu from source on RHEL/CentOS 6.
> Error seen while installing devtoolset-3
> {noformat}
> --2020-06-17 11:08:57--
> https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/noarch/rhscl-devtoolset-3-epel-6-x86_64-1-2.noarch.rpm
> Resolving www.softwarecollections.org... 209.132.183.215
> Connecting to www.softwarecollections.org|209.132.183.215|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location:
> /en/repos/rhscl/devtoolset-3/epel-6-x86_64/noarch/rhscl-devtoolset-3-epel-6-x86_64-1-2.noarch.rpm/
> [following]
> --2020-06-17 11:08:57--
> https://www.softwarecollections.org/en/repos/rhscl/devtoolset-3/epel-6-x86_64/noarch/rhscl-devtoolset-3-epel-6-x86_64-1-2.noarch.rpm/
> Reusing existing connection to www.softwarecollections.org:443.
> HTTP request sent, awaiting response... 404 Not Found
> 2020-06-17 11:08:57 ERROR 404: Not Found.
> Loaded plugins: ovl, priorities
> Setting up Install Process
> error: not an rpm package
> Cannot open: rhscl-devtoolset-3-epel-6-x86_64-1-2.noarch.rpm. Skipping.
> {noformat}
> Update instructions like following in documentation and docker build.
> https://kudu.apache.org/docs/installation.html#rhel_from_source
> {noformat}
> $ DTLS_RPM=rhscl-devtoolset-3-epel-6-x86_64-1-2.noarch.rpm
> $
> DTLS_RPM_URL=https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/noarch/${DTLS_RPM}
> $ wget ${DTLS_RPM_URL} -O ${DTLS_RPM}
> $ sudo yum install -y scl-utils ${DTLS_RPM}
> $ sudo yum install -y devtoolset-3-toolchain
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
