commit | 8feb4fd13e7ff496a6464ec23eaf7c14a396f2f3 | [log] [tgz] |
---|---|---|
author | Yang Guo <yangguo@chromium.org> | Tue Aug 07 10:37:03 2018 |
committer | Yang Guo <yangguo@chromium.org> | Tue Aug 07 10:37:03 2018 |
tree | 8910385be95a638c95acd30bc4c4e76700475fac | |
parent | 9ecb488594c8827b212e9fa1d66e041b18b8f8e8 [diff] |
Updated What to do if your CL broke the Node.js integration build (markdown)
diff --git a/What-to-do-if-your-CL-broke-the-Node.js-integration-build.md b/What-to-do-if-your-CL-broke-the-Node.js-integration-build.md index f1a3d81..b7c2b37 100644 --- a/What-to-do-if-your-CL-broke-the-Node.js-integration-build.md +++ b/What-to-do-if-your-CL-broke-the-Node.js-integration-build.md
@@ -61,7 +61,7 @@ Replace node/deps/v8 with a copy of v8 (lkgr branch) and build Node. ``` -$V8/tools/release/update_node.py $V8 $NODE +$V8/tools/node/update_node.py $V8 $NODE cd $NODE ./configure --build-v8-with-gn && make -j48 test ```