Log4j configuration is a difficult topic, because there's so many ways
to do it. I keep my log4j.properties file in the same directory as my
hadoop configuration XML files. One of the ways log4j finds its
log4j.properties file is by CLASSPATH, and the configuration directory
is always in the CLASSPATH.
I don't think anyone is doing a regular bug scrub on Solaris /
OpenIndiana unit test issues. This is an area where you could
definitely make a contribution. You should try with and without
-Pnative in order to narrow down the range of issues.
Once Maven runs cmake and sets up the Makefiles, you can run them just
via "make". This may be helpful if you want to iterate quickly. Also
please check the compiler warnings-- they often hide very serious
On Thu, Oct 10, 2013 at 12:33 AM, "Andreas Grüninger"
<[EMAIL PROTECTED]> wrote:
> I compiled the native libraries of 2.1.1 for OpenIndiana.
> When I run the tests to check my changes I get a lot of errors.
> When I run the tests without my changes I get nearly the same errors.
> I checked the tests with the current stable 1.2.1 too with/without native libraries.
> And I get there errors too, about 29 of 1522 (by heart, sitting at home).
> The inspection of the crash reports let me assume that there are errors the usage of fstat and IPC errors.
> Maybe some of you compile the source with OI or Solaris and can give some hints how to compile it. The compiler is gcc 4.6.2.
> I found the crash reports and the logs in build/test/....
> But I did not understand which log4j.properties must be changed to get DEBUG level information. And where to find it afterwards. I assume the same log files which now contains the log messages from log4j with debug level INFO. I found log4j.properties, changed to DEBUG, recompiled and repeated the tests, but to no avail.
> I would really like to change the source code but I need the logging of the DEBUG messages.
> TIA and Greetings