- Original Message -
> On 03/14/2013 08:58 AM, Alan Bateman wrote:
> > On 14/03/2013 01:26, David Holmes wrote:
> >> :
> >>
> >>> 3. -Werror is set for the SCTP native code causing the build to
> >>> fail:
> >>>
> >>> Lots of stuff like:
> >>>
> >>> /home/andrew/projects/openjdk/upstream
- Original Message -
> On 14/03/2013 01:26, David Holmes wrote:
> > :
> >
> >> 3. -Werror is set for the SCTP native code causing the build to
> >> fail:
> >>
> >> Lots of stuff like:
> >>
> >> /home/andrew/projects/openjdk/upstream/jdk8/jdk/src/solaris/native/sun/nio/ch/sctp/SctpChannel
On 03/14/2013 08:58 AM, Alan Bateman wrote:
On 14/03/2013 01:26, David Holmes wrote:
:
3. -Werror is set for the SCTP native code causing the build to fail:
Lots of stuff like:
/home/andrew/projects/openjdk/upstream/jdk8/jdk/src/solaris/native/sun/nio/ch/sctp/SctpChannelImpl.c:88:24:
error:
Hello Andrew,
Thanks for the feedback! Adding in my view of things below.
On 2013-03-13 17:16, Andrew Hughes wrote:
I've just got my first build out of the new system using the main jdk8/jdk8
tree (b80) and
so thought it was worth giving some feedback on the problems encountered and
issues
wi
On 14/03/2013 01:26, David Holmes wrote:
:
3. -Werror is set for the SCTP native code causing the build to fail:
Lots of stuff like:
/home/andrew/projects/openjdk/upstream/jdk8/jdk/src/solaris/native/sun/nio/ch/sctp/SctpChannelImpl.c:88:24:
error: unused parameter 'klass' [-Werror=unused-pa
Hi Andrew,
On 14/03/2013 2:16 AM, Andrew Hughes wrote:
I've just got my first build out of the new system using the main jdk8/jdk8
tree (b80) and
so thought it was worth giving some feedback on the problems encountered and
issues
with the end result:
1. It took some time to work out how to g
- Original Message -
> On 3/13/13 7:35 PM, Andrew Hughes wrote:
> > I still think it should be a configure option, which is the first
> > place I looked.
>
> You'd usually use it if something interesting happens, like a build
> failure, and
> it's a you're 'not sure how it could have come
Ugh. effect -> affect. An unforgivable mistake.
Mike
On Mar 13 2013, at 12:18 , Mike Duigou wrote:
> I generally agree that logging is something I want to tune dynamically.
> Logging is one of the few things I prefer as an environment variable.
>
> As a compromise though perhaps a configure op
I generally agree that logging is something I want to tune dynamically. Logging
is one of the few things I prefer as an environment variable.
As a compromise though perhaps a configure option to adjust the default logging
level might work. Still overridable via LOG but with a configurable defaul
On 3/13/13 7:35 PM, Andrew Hughes wrote:
> I still think it should be a configure option, which is the first place I
> looked.
You'd usually use it if something interesting happens, like a build failure,
and
it's a you're 'not sure how it could have come to this' situation, so in that
case,
h
- Original Message -
> On 03/13/2013 12:16 PM, Andrew Hughes wrote:
> > 1. It took some time to work out how to get back to the usual
> > 'noisy' build as the
> > default seems to subdue all the useful output. VERBOSE=true broke
> > the build when
> > it tried to use 'true' as a Makefile
On 03/13/2013 12:16 PM, Andrew Hughes wrote:
> 1. It took some time to work out how to get back to the usual 'noisy' build
> as the
> default seems to subdue all the useful output. VERBOSE=true broke the build
> when
> it tried to use 'true' as a Makefile target. It turns out the solution is
I've just got my first build out of the new system using the main jdk8/jdk8
tree (b80) and
so thought it was worth giving some feedback on the problems encountered and
issues
with the end result:
1. It took some time to work out how to get back to the usual 'noisy' build as
the
default seems t
13 matches
Mail list logo
