Changeset: b66c81dfa291
Author:ohair
Date: 2013-01-14 16:38 -0800
URL: http://hg.openjdk.java.net/jdk8/build/rev/b66c81dfa291
8005284: build-infra: nonstandard copyright headers under
common/autoconf/build-aux
Reviewed-by: katleman
! common/autoconf/build-aux/autoconf-config.guess
Ok from me.
-kto
On Jan 14, 2013, at 5:24 AM, Erik Joelsson wrote:
> This didn't quite work as I expected. Found the issue in needing to include
> SPEC before Jprt.gmk so that variables from SPEC would be available in
> Jprt.gmk at parse time.
>
> http://cr.openjdk.java.net/~erikj/8006100/web
Just a nit, but configure is quite happy to use the PATH environment variable,
not that it mentions this anywhere in the output of "sh configure help". Yes,
I know that PATH is implicit, yes, I know that I am complaining about Unix
documentation, yes I know that the new build system is in fact
On 14/01/2013 13:24, Erik Joelsson wrote:
This didn't quite work as I expected. Found the issue in needing to
include SPEC before Jprt.gmk so that variables from SPEC would be
available in Jprt.gmk at parse time.
http://cr.openjdk.java.net/~erikj/8006100/webrev.root.02/
/Erik
Thanks Erik, I'v
Erik:
This didn't quite work as I expected. Found the issue in needing to
include SPEC before Jprt.gmk so that variables from SPEC would be
available in Jprt.gmk at parse time.
http://cr.openjdk.java.net/~erikj/8006100/webrev.root.02/
Looks good.
Tim
/Erik
On 2013-01-11 17:25, Erik Joe
This didn't quite work as I expected. Found the issue in needing to
include SPEC before Jprt.gmk so that variables from SPEC would be
available in Jprt.gmk at parse time.
http://cr.openjdk.java.net/~erikj/8006100/webrev.root.02/
/Erik
On 2013-01-11 17:25, Erik Joelsson wrote:
This fixes the b
Hello,
I'm trying to build JDK using previously built Hotspot/JDK as a
bootstrap. Everything seems to work fine until it comes to BridgeSupport:
Updating bridge support in
/Users/karnaukhovv/projects/tmp/jdk/build/bridge_metadata
(cd /Users/karnaukhovv/projects/tmp/jdk/build/bridge_metadata;
Hello,
The help text produced by autoconf is part specific to our scripts and
part is standard autoconf stuff. The variable section is part of the
standard help. It's bad that the script isn't behaving as the help text
suggests and we should try to fix that if possible. We definitely need
to
