RTEMS | waf exits too early when building all BSPs at once (#5252)

[Joel Sherrill (@joel)]

Joel Sherrill created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5252



## Summary
I am experimenting with various config.ini files that specified building all BSPs in an architecture or all BSPs across all architectures. I am building with _waf -k_ but it is exiting after arm. At least one of the arm BSPs has a linking error in a test. _waf_ continues on through that architecture but not through the others.

## Steps to reproduce

Using the attached file config-all.ini, build as follows:

```
./waf configure --rtems-config=config-all.ini
time ./waf -k >b-all.log 2>&1 &
```

Since at least the csb336 has a linking error, the build stops at arm and does not attempt any other architectures. Check b-all.log for details.

This  is reproducible with just a BSP that fails to build from one architecture (currently arm/csb336) and any other BSP from another architecture which currently builds (sparc/leon3). The following config-two.ini file reproduces the failure:

```
[arm/csb336]
BUILD_SAMPLES=True
BUILD_TESTS=True

[sparc/leon3]
BUILD_SAMPLES=True
BUILD_TESTS=True
```

Build as follows.

```
./waf configure --rtems-config=config-two.ini
time ./waf -k >b-two.log 2>&1 &
```

Check _b-two.log_ and there are no files built for sparc/leon3. The directories are in the build tree but _waf_ did not transition to the second architecture.

### Pre-set options

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5252
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250526/919daa8a/attachment.htm>