I went to the /patches/make directory and executed the make command as follows.
1) make setup, to create symbolic link and set guard. The last output is:
------------------------
# report what happened:
cd ../..; bash patches/make/each-patch-repo.sh 'hg qselect; hg qunapplied'
+ (cd sources/.; hg qselect; hg qunapplied)
0b66a233bfb9
buildable
testable
+ (cd sources/hotspot; hg qselect; hg qunapplied)
buildable
d8cb48376797
testable
+ (cd sources/jdk; hg qselect; hg qunapplied)
7ab0d613cd1a
buildable
testable
meth-acc-7077803.patch
cval-tune-7030453.patch
meth.patch
meth-experiment.patch
continuation.patch
anonk.patch
coro.patch
+ (cd sources/langtools; hg qselect; hg qunapplied)
5df63fd8fa64
buildable
testable
------------------------
2) make check, I got errors, so I continued to do,
3) make force
4) make check, to review if the force command had been taken into effect. the
output is:
------------------------
# check the difference betwen tip version and patch-required version, if there
is difference,
# then create file current-diffs.txt in the source repo and exit with 1
# If this command fails, consider setting RELAX_CHECKS=true or
FORCE_VERSIONS=true.
cd ../..; bash patches/make/each-patch-repo.sh \
hg diff --git -I src -r "\$(bash
`pwd`/patches/make/current-release.sh)" \
"> current-diffs.txt;" \
"if [ ! -s current-diffs.txt ]; then rm current-diffs.txt;" \
"else grep '^diff' current-diffs.txt; exit 1; fi"
+ (cd sources/.; hg diff --git -I src -r $(bash
/home/xc1427/continuation_research/davinci.v1/patches/make/current-release.sh)
> current-diffs.txt; if [ ! -s current-diffs.txt ]; then rm current-diffs.txt;
else grep '^diff' current-diffs.txt; exit 1; fi)
+ (cd sources/hotspot; hg diff --git -I src -r $(bash
/home/xc1427/continuation_research/davinci.v1/patches/make/current-release.sh)
> current-diffs.txt; if [ ! -s current-diffs.txt ]; then rm current-diffs.txt;
else grep '^diff' current-diffs.txt; exit 1; fi)
mq status file refers to unknown node 4c9ea0147722
mq status file refers to unknown node daf841a4cc84
+ (cd sources/jdk; hg diff --git -I src -r $(bash
/home/xc1427/continuation_research/davinci.v1/patches/make/current-release.sh)
> current-diffs.txt; if [ ! -s current-diffs.txt ]; then rm current-diffs.txt;
else grep '^diff' current-diffs.txt; exit 1; fi)
mq status file refers to unknown node f2029fe990b5
mq status file refers to unknown node f2029fe990b5
+ (cd sources/langtools; hg diff --git -I src -r $(bash
/home/xc1427/continuation_research/davinci.v1/patches/make/current-release.sh)
> current-diffs.txt; if [ ! -s current-diffs.txt ]; then rm current-diffs.txt;
else grep '^diff' current-diffs.txt; exit 1; fi)
mq status file refers to unknown node 0001c23b2b4b
mq status file refers to unknown node 0001c23b2b4b
------------------------
we can notice the strange message as "refers to unknow node XXXX". However,
there is no more error.
5) make patch. This is where I failed. the output is:
------------------------
cd ../..; bash patches/make/each-patch-repo.sh \
'(! hg qunapplied | read something) || hg qpush -a'
+ (cd sources/.; (! hg qunapplied | read something) || hg qpush -a)
+ (cd sources/hotspot; (! hg qunapplied | read something) || hg qpush -a)
+ (cd sources/jdk; (! hg qunapplied | read something) || hg qpush -a)
mq status file refers to unknown node f2029fe990b5
(working directory not at a head)
abort: working directory revision is not qtip
*** Exit status 255.
+ (cd sources/langtools; (! hg qunapplied | read something) || hg qpush -a)
make: *** [mq-push-patches] Error 255
------------------------
As we see, the error comes out as "working directory revision is not qtip". I
searched in google and mercurial wiki, but found few helpful informations.
== My point of view ==
I've ever tried "hg qapplied" in the sources/hotspot right after the first
step. I got supprised by the output:
----------
mac-tweaks.patch
meth.patch
coro-meth.patch
coro.patch
----------
which means some patches had been applied before I did nothing. And recall the
previous strange message "refers to unknow node XXXX".
I got frustrated at the very first stage. Can somebody help me?
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
