The JDK build generates a whole lot of warnings along the way. This is
bad because these warnings can sometimes mask real errors. For a
variety of reasons, it appears to be hard to try and get rid of all the
warnings, so this message is about a set of possible ideas to try and
get some control ove
The maintainer of GNU make makes a commitment here:
http://article.gmane.org/gmane.comp.gnu.make.windows/2937
to fix the problem in 3.82
On Mon, 2008-06-30 at 18:08 -0700, Kelly O'Hair wrote:
> I assume cygwin will not be fixing this, in 3.82 or ever, is that
> the conclusion I am seeing?
One significant simple annoyance is that compile errors are hard to find
amongst the mass of warnings, because errors are not identified as such.
It would be very nice if errors were prefixed by "error:" the same
way that warnings are prefixed by "warning:",
making them easy to search for.
Martin
The point is noted, but it seems to me that it would be better to
work on removing warnings rather than making it even easier
to continue ignoring them :-)
With the possible exception of the obnoxious proprietary API
warnings from javac (which typically do not occur in the build
anyway), all warn
+1 from me.
---
It might help that when people do remove some of the more tricky
warnings, that they send a short email on how they did it.
I remember having to walk down the hall to see Peter Ahe a few times
when I was trying to get rid of some of the trickier warnings in some
of my java code.
Thanks Martin.
The GNU Make people claim it's fixed, but CYGWIN in general will
probably continue to have issues with MS-DOS style paths.
The basic OpenJDK Makefile rules I'm trying to follow will be:
* Avoid full paths if at all possible, use relative paths or
limit the commands/utilitie
I am hacking inside the JRE native libraries just for fun, having troubles to
track a crash down.
Is it possible to build OpenJDK with debugging symbols included in external
native libraries like libzip.so, and if it is how can I enable it?
Mfg regina
Hi Regina,
set FASTDEBUG=true to enable debug symbols (with compiler
optimizations enabled), or DEBUG=true to get a build with
compiler opt. disabled (and I believe a debug runtime will
be used on windows in this case as well).
I recommend using FASTDEBUG=true - the resulting binar
With a separate cloned jdk repository, try running 'cd make && gmake debug'
It should compile everything with -g.
Then copy the libzip.so into the JDK you are playing with, that way
just the debug version of libzip.so is used instead of the entire
debug jdk. That's assuming you have isolated th
