I’m compile Komodo IDE 9 and my PC just rebooted when I compile libxul.so (it’s caused by small size of RAM). Can I continue compiling if it’s stopped? If can - how to do?
hey Defman,
You should be able to run
python build.py all
and it will try to pickup where it left off.
If that doesn’t work though you’ll have to use
python build.py distclean all
It’s probably faster to mv
mozilla/build aside, start your new build and then rm
the old build folder while the new build runs.
- Carey
It’s give me this:
target: patch mozilla from ['patches-new']
apply 'autoupdate_base_dir.patch'
can't find file to patch at input line 15
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From 0413f96586e9d9bed1fb72e674a7f314c7675f70 Mon Sep 17 00:00:00 2001
|From: Mark Yen <marky+git@activestate.com>
|Date: Tue, 18 Dec 2012 15:18:16 -0800
|Subject: [PATCH] updater: go up two directories from appdir, due to different
| application layout in komodo
|
|---
| toolkit/mozapps/update/updater/updater.cpp | 13 +++++++++++++
| 1 file changed, 13 insertions(+)
|
|diff --git a/toolkit/mozapps/update/updater/updater.cpp b/toolkit/mozapps/update/updater/updater.cpp
|index 74bb1ec..c1469cf 100644
|--- a/toolkit/mozapps/update/updater/updater.cpp
|+++ b/toolkit/mozapps/update/updater/updater.cpp
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
Traceback (most recent call last):
File "build.py", line 3017, in <module>
sys.exit( main(sys.argv) )
File "build.py", line 3013, in main
return build(args)
File "build.py", line 2837, in build
newArgv = targetFunc(argv)
File "build.py", line 2520, in target_all
target_patch()
File "build.py", line 2569, in target_patch
logFilename=logFilename)
File "../util/patchtree.py", line 1101, in patch
workDir, patchArgs=action[3])
File "../util/patchtree.py", line 626, in _applyPatch
% (patchFile, inReverse, argv, sourceDir, retval))
patchtree.Error: error applying patch '/tmp/tmptF9iDC/patchlog/autoupdate_base_dir.patch': argv=['/usr/bin/patch', '-f', '-p0', '-g0', '-p1'], cwd='/tmp/tmptF9iDC/workdir', retval=1
It’s a fatal error or not?
Did you try python build distclean all yet?
If that’s what happens when you tried to restart the build, it may not be able to recover. You could try looking at the patch file and see what it’s referring to here:
- Carey
No I did not. I’m get this error when run python build.py all
. I’m try to python build distclean all
later
I’m look into this patch…
I can’t view this patch cuz it’s created in /tmp/
and removed after error. I’m try python build distclean all
later (tomorrow).
Note depending on what part of the build process you interrupted it may not be able to resume building. Aborting during patches is generally a bad time and will result in a corrupt build, you should restart your build with python build.py distclean all
.
Just providing context.