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

Josh Elser commented on HBASE-20356:
------------------------------------

{quote}Does dropping it make it harder for current folk to upgrade?
{quote}
Under the same premise, I don't think there is any runtime impact, so there 
should be no upgrade issues.
{quote}If CentOS has runway until 2020, then is it wise to drop from our build 
target list?
{quote}
It's definitely a balancing act. I'd equate Centos6 to some stone-age Linux 
software at this point. While this is what "enterprises want", the cost we pay 
is that we have to limit ourselves in what we can use. That mindset (not being 
able to control our build-environment) is what makes me think that this is 
something better to bite the bullet on now, rather than let it control our 
destiny.

> protoc 3.5.1 can't compile on rhel6
> -----------------------------------
>
>                 Key: HBASE-20356
>                 URL: https://issues.apache.org/jira/browse/HBASE-20356
>             Project: HBase
>          Issue Type: Bug
>          Components: dependencies, thirdparty
>    Affects Versions: 2.0.0-beta-2
>            Reporter: Mike Drob
>            Priority: Blocker
>             Fix For: 2.0.0, thirdparty-2.2.0
>
>
> We upgraded our internal protoc version, and now can't build on RHEL6.
> I get this build error:
> {noformat}
> 2018-04-05 08:15:21.929278 [ERROR] PROTOC FAILED: ... /lib64/libc.so.6: 
> version `GLIBC_2.14' not found
> {noformat}
> See https://github.com/google/protobuf/issues/4109
> And this has come up before in https://github.com/google/protobuf/issues/3718
> Looks like we need to be on 3.4.0, unless there's a compelling reason to be 
> on something newer? Maybe roll back all the way to 3.3.0 which is what we 
> were on before... was there a specific bug we needed to get addressed?
> cc: [~elserj] [~stack]



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

Reply via email to