Unused DEBUG_CLASSFILES variable in makefiles

Omair Majid omajid at redhat.com
Wed Feb 11 22:52:24 UTC 2015


* Omair Majid <omajid at redhat.com> [2014-11-18 11:57]:
> * Magnus Ihse Bursie <magnus.ihse.bursie at oracle.com> [2014-10-13 07:49]:
> > On 2014-10-13 10:57, Erik Joelsson wrote:
> > >I think it's still used by the hotspot makefiles (sa-jdi.jar). Seems weird
> > >that we still set it in configure but then ignore the value in the jdk
> > >build. I would vote for resurrecting the option.
> > [...]
> > >I'm not sure if even more debug levels is the right way to go. It seems
> > >hard to name and that probably means it will be hard to understand.
> > >Perhaps completely separating native debug level and java debug level
> > >would make more sense?
> > 
> > I'm not sure "resurrecting" (which actually means adding functionality which
> > has been gone for quite some time now) is good, since it adds to the
> > complexity.
> Well, we do need the debug information, but I am not at all tied to
> specific implementation. I would be happy to try and implement something
> that takes a different approach than resurrecting the feature.
> > However, there have been recurring requests of having more control of debug
> > vs release builds, and I think we need to address them in some way.
> Any suggestions for a suitable implementation?

Sorry to resurrect an old thread, but this just bit me again. Any
suggestions on how to get the equivalent of DEBUG_CLASSFILES back and/or
ensure that -g is the default everywhere on OpenJDK builds?


PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681

More information about the build-dev mailing list