Mike Drob commented on HBASE-20356:

bq. For CentOS6 users, they'd use earlier hbase-thirdparty? Or should we build 
them a version of hbase-thirdparty that has updated cli and old pb?
Yea, I think we'd have to do this...

I've been digging into what it would take otherwise, and it's not looking 
pretty. I followed the instructions at https://stackoverflow.com/a/38317265 to 
add a new glibc to my CentOS image, and that part seemed to work. However, when 
I export the new LD_LIBRARY_PATH then mvn commands hang, I wonder if that 
screws up the JVM native calls somewhere...?

Currently trying to see what happens if I downgrade the version of the compiler 
used but don't change the version of thirdparty used... Any idea where we would 
expect the tests to fail if that were an issue, otherwise I have a lot of 
territory to try and cover.

> 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

Reply via email to