[jira] [Commented] (KUDU-2427) Add support for Ubuntu 18.04

["Grant Henke (JIRA)" <ji...@apache.org>]

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

Grant Henke commented on KUDU-2427:
-----------------------------------

We may want to break out the Java 9/10 compilation/test issues into another Jira but I will list the known ones here for now:
* error-prone has an outdated compiler and because it replaces javac it needs to be updated.
** https://github.com/google/error-prone/issues/860
* The gradle javadoc task is failing with `javadoc: error - invalid flag: -d`
** Not sure about this yet but I will look into it.
* KUDU-2403: We need to find a new way to prevent localhost dns in unit tests.




> Add support for Ubuntu 18.04
> ----------------------------
>
>                 Key: KUDU-2427
>                 URL: https://issues.apache.org/jira/browse/KUDU-2427
>             Project: Kudu
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.8.0
>            Reporter: Adar Dembo
>            Assignee: Adar Dembo
>            Priority: Major
>
> Ubuntu 18.04 (Bionic) is out, and since it's the next LTS release from Ubuntu we should support it. Unlike previous releases, this one is chock full of Kudu-breaking changes. It's getting difficult for me to keep track of them all, so I'll use this Jira to do that.
> h3. New Java
> Bionic ships with both JDK8 and JDK10, but defaults to JDK10. I'm sure that'll lead to a number of issues with our Java bindings. Most immediately, though, is [this cmake bug|https://gitlab.kitware.com/cmake/cmake/issues/17938] which prevents cmake from finding the JDK via find_package(Java). The bug fix is scheduled for 3.11.2 which has yet to be released; Bionic ships with a version of cmake 3.10 that has been patched to include this fix.
> h3. New gcc
> Bionic ships with gcc5, gcc6, gcc7, and gcc8, but defaults to gcc7. Beyond the usual set of new warnings, this version of gcc cannot compile breakpad. [This bug|https://bugs.chromium.org/p/google-breakpad/issues/detail?id=739] was filed, and it seems to have been fixed in the top of the breakpad tree, perhaps in [this commit|https://chromium.googlesource.com/breakpad/breakpad/+/bddcc58860f522a0d4cbaa7e9d04058caee0db9d].
> h3. New OpenSSL
> Bionic ships with libssl1.0 and 1.1, but defaults to 1.1. The transition from 1.0 to 1.1 [broke all sorts of ABIs and APIs|https://abi-laboratory.pro/tracker/objects_report/openssl/1.0.2o/1.1.0/report.html], some of which have been documented by KUDU-1889.
> h3. Miscellaneous stuff
> I'm still working through several test failures that I can't yet attribute to any one particular thing. These are:
>  # Some tests that depend on libkudu_util.so appear to load that before loading libc, which causes the dl_iterate_phdr dlsym() call in util/debug/unwind_safeness.cc to fail at startup. Commenting that out leads to deadlocks in debug-util-test, so whatever underlying race existed in libc still exists.
>  # All of the tests in minidump-test fail, probably due to changes in breakpad.
>  # Symbolization via google::Symbolize appears to produce  "(unknown)" frames in code that has been statically linked. Perhaps the problem is not so generic, but this leads to failures in stack_watchdog-test, which expects to find the name of the test in one of the stack frames.



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