At 10:48 PM -0500 3/3/12, Stephen Bannasch wrote:
On Mar 3, 2012, at 4:53 PM, Stephen Bannasch wrote:
I cloned the forest
<http://hg.openjdk.java.net/jdk8/tl/>http://hg.openjdk.java.net/jdk8/tl/ into
sources
No, we moved to
<http://hg.openjdk.java.net/hsx/hotspot-comp>http://hg.openjdk.java.net/hsx/hotspot-comp
a while ago. See:
<http://hg.openjdk.java.net/mlvm/mlvm/file/tip/README.txt>http://hg.openjdk.java.net/mlvm/mlvm/file/tip/README.txt
Regarding step 3: Add Michael's patches to jdk. (Crucial!)
For the time being you have already added this patch to the mlvm patch set as:
'macosx-7113349.patch' right?
Yes. When the final version of those changes gets down into
hsx/hotspot-comp/jdk, I'll deletethat patch.
I've set the guards to: "buildable testable"
I added a .rvmrc file in the main dir to make sure the Ruby 1.8.7 is selected
(needed to build jobjc).
I'm getting an unknown revision error trying to patch hotspot:
*** running: hg update -r
+ (cd sources/.; hg update -r $(sh $davinci/patches/make/current-release.sh))
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
+ (cd sources/hotspot; hg update -r $(sh
$davinci/patches/make/current-release.sh))
abort: unknown revision 'b279f99d7143'!
Were you basing this on the jdk8/tl forest?
No, and revision b279f99d7143 has not arrived there yet.
OK, using jdk8/tl (wrong forest) I obviously didn't get the patches applied correctly to hotspot but the build completed and
works well enough to respond with it's version number:
$ ./build/macosx-amd64/j2sdk-bundle/1.8.0.jdk/Contents/Home/bin/java -version
openjdk version "1.8.0-internal"
OpenJDK Runtime Environment (build
1.8.0-internal-stephen_2012_03_03_19_47-b00)
OpenJDK 64-Bit Server VM (build 23.0-b16, mixed mode)
Also the jdk/test/java/lang/invoke/ tests passed
Trying with the hsx/hotspot-comp forest I don't get nearly as far:
rm -rf sources
hg fclone http://hg.openjdk.java.net/hsx/hotspot-comp sources
. update.sh
The script update.sh is here: https://gist.github.com/243072
Basically the errors start when I run: hg qselect --pop $guards.
Ack ... it turns out that if I delete and re-create the sources dir with another forest I'll get these kind of errors unless I
also delete and re-create the patches forest.
... probably something to do with the symbolic links between the two -- I could probably fix it without recreating the patches
forest -- but I just re-created it and the build is progressing properly now ..._______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev