workaround install toolchain
Posted: Thu Dec 03, 2015 11:23 am
hi guys
i wrote, that a little broken was here in my VM at install the toolchain
so i switch to debug mode in ct-ng and get then in second build this:
[INFO ] Installing cross-gdb
[ERROR] configure: error: expat is missing or unusable
[ERROR] make[2]: *** [configure-gdb] Error 1
[ERROR] make[1]: *** [all] Error 2
[ERROR] |
[ERROR] >>
[ERROR] >> Build failed in step 'Installing cross-gdb'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR] >> called from: do_debug_gdb_build[scripts/build/debug/300-gdb.sh@181]
[ERROR] >> called from: do_debug[scripts/build/debug.sh@35]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@638]
/
Current command:
'make' '-j2' '-l'
exited with error code: 2
Please fix it up and finish by exiting the shell with one of these values:
1 fixed, continue with next build command
2 repeat this build command
3 abort build
expat was missing / unusable
i was unsure, had installed it but i try so i do again
sudo apt-get install expat btw.
so here a little workaround if you have same problem:
try to install expat if you do not have
and if you run the crosstool-ng in debug mode you can read more infos
and can go on in the broken process again. you must then not start
from begin:
yes, current crosstool-ng has support this feature.
enable this feature in menuconfig
for ct-ng menuconfig, config Paths and misc options like this
─Paths and misc options ─
[*] Debug crosstool-NG
[ ] Pause between every steps
[*] Save intermediate steps
[*] gzip saved states
[*] Interactive shell on failed commands
when do build, for each step done successfully, you will see something like this:
Saving state to restart at step 'xxx'...
when fail, after fix it, then use ct-ng LAST_SUCCESSFUL_STETP_NAME+ to continue build
my example:
ct-ng:/opt/Espressif/crosstool-NG> ./ct-ng list-steps
make[2]: Entering directory `/opt/Espressif/crosstool-NG'
Available build steps, in order:
- libc_check_config
- companion_libs_for_build
- binutils_for_build
- companion_libs_for_host
- binutils_for_host
- cc_core_pass_1
- kernel_headers
- libc_start_files
- cc_core_pass_2
- libc
- cc_for_build
- cc_for_host
- libelf_for_target
- binutils_for_target
- debug (here in my install was broken)
- test_suite
- finish
Use "<step>" as action to execute only that step.
Use "+<step>" as action to execute up to that step.
Use "<step>+" as action to execute from that step onward.
make[2]: Leaving directory `/opt/Espressif/crosstool-NG'
so i can start here in this process and must not start from begin
ct-ng:/opt/Espressif/crosstool-NG> ./ct-ng debug+
make[2]: Entering directory `/opt/Espressif/crosstool-NG'
[INFO ] Performing some trivial sanity checks
[INFO ] Build started 20151203.173555
[INFO ] Building environment variables
[INFO ] Restoring state at step 'debug', as requested.
[INFO ] =================================================================
[INFO ] Installing cross-gdb
[INFO ] Installing cross-gdb: done in 1454.82s (at 24:50)
[INFO ] Saving state to restart at step 'test_suite'...
[INFO ] Saving state to restart at step 'finish'...
[INFO ] =================================================================
[INFO ] Cleaning-up the toolchain's directory
[INFO ] Stripping all toolchain executables
[INFO ] Cleaning-up the toolchain's directory: done in 14.95s (at 26:41)
[INFO ] Build completed at 20151203.180232
[INFO ] (elapsed: 401:28.41)
[INFO ] Finishing installation (may take a few seconds)...
[26:41] / make[2]: Leaving directory `/opt/Espressif/crosstool-NG'
ct-ng:/opt/Espressif/crosstool-NG>
and done!
my second workaround:
think there is a little mistake in "Project Template Compile" Part,
must add
cd ~/Workspace/project_template
before Step 6
make clean
make
because we are in ~/Workspace
( See Step 2 in this Part )
and there is no MAKEFILE
best wishes
rudi
btw:
i installed code::blocks for the first ESP32-Hello World in the lubuntu VM
if you want see this, i update today here with a small video from output.
i wrote, that a little broken was here in my VM at install the toolchain
so i switch to debug mode in ct-ng and get then in second build this:
[INFO ] Installing cross-gdb
[ERROR] configure: error: expat is missing or unusable
[ERROR] make[2]: *** [configure-gdb] Error 1
[ERROR] make[1]: *** [all] Error 2
[ERROR] |
[ERROR] >>
[ERROR] >> Build failed in step 'Installing cross-gdb'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR] >> called from: do_debug_gdb_build[scripts/build/debug/300-gdb.sh@181]
[ERROR] >> called from: do_debug[scripts/build/debug.sh@35]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@638]
/
Current command:
'make' '-j2' '-l'
exited with error code: 2
Please fix it up and finish by exiting the shell with one of these values:
1 fixed, continue with next build command
2 repeat this build command
3 abort build
expat was missing / unusable
i was unsure, had installed it but i try so i do again
sudo apt-get install expat btw.
so here a little workaround if you have same problem:
try to install expat if you do not have
and if you run the crosstool-ng in debug mode you can read more infos
and can go on in the broken process again. you must then not start
from begin:
yes, current crosstool-ng has support this feature.
enable this feature in menuconfig
for ct-ng menuconfig, config Paths and misc options like this
─Paths and misc options ─
[*] Debug crosstool-NG
[ ] Pause between every steps
[*] Save intermediate steps
[*] gzip saved states
[*] Interactive shell on failed commands
when do build, for each step done successfully, you will see something like this:
Saving state to restart at step 'xxx'...
when fail, after fix it, then use ct-ng LAST_SUCCESSFUL_STETP_NAME+ to continue build
my example:
ct-ng:/opt/Espressif/crosstool-NG> ./ct-ng list-steps
make[2]: Entering directory `/opt/Espressif/crosstool-NG'
Available build steps, in order:
- libc_check_config
- companion_libs_for_build
- binutils_for_build
- companion_libs_for_host
- binutils_for_host
- cc_core_pass_1
- kernel_headers
- libc_start_files
- cc_core_pass_2
- libc
- cc_for_build
- cc_for_host
- libelf_for_target
- binutils_for_target
- debug (here in my install was broken)
- test_suite
- finish
Use "<step>" as action to execute only that step.
Use "+<step>" as action to execute up to that step.
Use "<step>+" as action to execute from that step onward.
make[2]: Leaving directory `/opt/Espressif/crosstool-NG'
so i can start here in this process and must not start from begin
ct-ng:/opt/Espressif/crosstool-NG> ./ct-ng debug+
make[2]: Entering directory `/opt/Espressif/crosstool-NG'
[INFO ] Performing some trivial sanity checks
[INFO ] Build started 20151203.173555
[INFO ] Building environment variables
[INFO ] Restoring state at step 'debug', as requested.
[INFO ] =================================================================
[INFO ] Installing cross-gdb
[INFO ] Installing cross-gdb: done in 1454.82s (at 24:50)
[INFO ] Saving state to restart at step 'test_suite'...
[INFO ] Saving state to restart at step 'finish'...
[INFO ] =================================================================
[INFO ] Cleaning-up the toolchain's directory
[INFO ] Stripping all toolchain executables
[INFO ] Cleaning-up the toolchain's directory: done in 14.95s (at 26:41)
[INFO ] Build completed at 20151203.180232
[INFO ] (elapsed: 401:28.41)
[INFO ] Finishing installation (may take a few seconds)...
[26:41] / make[2]: Leaving directory `/opt/Espressif/crosstool-NG'
ct-ng:/opt/Espressif/crosstool-NG>
and done!
my second workaround:
think there is a little mistake in "Project Template Compile" Part,
must add
cd ~/Workspace/project_template
before Step 6
make clean
make
because we are in ~/Workspace
( See Step 2 in this Part )
and there is no MAKEFILE
best wishes
rudi
btw:
i installed code::blocks for the first ESP32-Hello World in the lubuntu VM
if you want see this, i update today here with a small video from output.