Closed 0xc0170 closed 5 years ago
One of the jobs affected: https://github.com/ARMmbed/mbed-os/pull/9738#issuecomment-469467096
ARMC6 landed without exporters test for armc6 make: https://github.com/ARMmbed/mbed-os/pull/9888#issuecomment-468877250
:388:10: fatal error: 'mbed_config.h' file not found #include "./mbed_config.h"
@ARMmbed/mbed-os-tools This might indicate a bug in our code, however mbed_config.h
has been working with make or others. Please review, this is blocking yours 2 PRs for 5.12rc1 (besides others)
https://github.com/ARMmbed/mbed-os/blob/master/tools/toolchains/__init__.py#L853
failure:
self.config_file = join(self.build_dir, self.MBED_CONFIG_FILE_NAME) // './mbed_config.h'
success:
import os self.config_file = os.path.abspath(join(self.build_dir, self.MBED_CONFIG_FILE_NAME)) // '/builds/ws/mbed-os-ci_exporter-make_armc6_3/examples/mbed-os-example-mesh-minimal/mbed_config.h'
or join(os.path.abspath(self.build_dir), self.MBED_CONFIG_FILE_NAME)
@alekla01 Using an abspath will kill all exports from the online compiler.
I have root-caused the issue here: Adding the include paths to the assembler command line is the problem. Specifically, the Makefile we export is a little sophisticated, and runs the compiler from within the build directory. The assembly preprocessing does not take this into account, and creates include paths that won't exist in the build directory.
-> '..' instead of abspath, ok
I have root-caused the issue here: Adding the include paths to the assembler command line is the problem. Specifically, the Makefile we export is a little sophisticated, and runs the compiler from within the build directory. The assembly preprocessing does not take this into account, and creates include paths that won't exist in the build directory.
How to fix this? 5.12 rc1 is blocked on this issue.
I'm taking a look at this now.
Description
Creating tracking issue for this as it seems no rootcase found so far.
Recent nightly and some PRs failed exporters job (since yesterday as soon as make armc6 got actived in the exporters).
The failure indicates a problem with
mbed_config.h
file include in the assembly files. This is the log from CI:Interesting part, I was able to reproduce the same failure but only if I had armc5 in paths as well (and many other failures because of different armasm) - using windows. Our CI that is failing has only ARMC6 installed, it's linux based machine.
Locally, executed
python -u mbed-os/tools/test/examples/examples.py export make_armc6 --mcu K66F
This is the error I get:
Same error if I run just
make
in the example blinky (using make 4.2 or 3.81)Too long command?
@SenRamakri @ARMmbed/mbed-os-test
Issue request type