On Thu, Jul 16, 2020 at 2:24 AM Thorsten Schöning <tschoen...@am-soft.de> wrote:
> Am I correct that you are using JDK 11 already? Because I'm running
> into problems when executing Maven in my UB 16.04 with JDK 8 setup a
> while ago.
>
Correct, Java 11 and Maven 3.6.3 for me. I'm on Debian 10, so Java 11
is readily available and I simply downloaded the latest version of
maven and put it on my $PATH to execute.
> > I'm not sure if the autotools still work at this point; I haven't
> > tested with them in a while.
>
> I just did and they compiled the project fine, the only test failing
> is most likely related to my setup:
>
> > log4cxx: Cannot get information about host: unknown.invalid
> > log4cxx: Could not find unknown.invalid. All logging will FAIL.
> > log4cxx: Cannot get information about host: unknown.invalid
>
> I have a proper name in /etc/hostname, so does anyone have an idea?
>
> > apr_sockaddr_t* address = 0;
> > apr_status_t status =
> > apr_sockaddr_info_get(&address, encodedHost.c_str(),
> > APR_INET, 0, 0, addrPool.getAPRPool());
> >
> > if (status != APR_SUCCESS)
> > {
> > LogString msg(LOG4CXX_STR("Cannot get information about
> > host: "));
> > msg.append(host);
> > LogLog::error(msg);
> > throw UnknownHostException(msg);
> > }
>
> > ping ub-16-04-lts-server-x64
> > PING ub-16-04-lts-server-x64 (127.0.1.1) 56(84) bytes of data.
> > 64 bytes from ub-16-04-lts-server-x64 (127.0.1.1): icmp_seq=1 ttl=64
> > time=0.017 ms
>
> > ping 0.0.0.0
> > PING 0.0.0.0 (127.0.0.1) 56(84) bytes of data.
> > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.017 ms
>
> > ping unknown.invalid
> > ping: unknown host unknown.invalid
>
> Not sure when I executed tests the last time, might be with UB 14.04.
>
Which test is this?
> > I guess that's one way of thinking about it. However, if you do that
> > it seems like you should always run all tests, while (for example) the
> > NT Event Logger appender test is only run on Windows; this would
> > always fail on Linux/OSX.
>
> Running only those tests which are designed for some platform at all
> and most likely to succeed with somewhat easy setup does read like a
> good compromise to me. SED and Co. are really easy to provide on
> Windows, for many users of GIT or WSL already available.
>
So perhaps the best solution is based a little bit off of Stephen's
earlier PR(#18[1]), but instead of compiling out the code that depends
on gzip we make the test more granular(one test for rolling zip, one
test for rolling gz, etc) and disable[2] the test if the appropriate
executable is not found.
-Robert Middleton
[1]: https://github.com/apache/logging-log4cxx/pull/18
[2]: https://cmake.org/cmake/help/latest/prop_test/DISABLED.html
