On Wed, Mar 25, 2020 at 12:46 PM Sid Spry <sid@xxxxxxx> wrote: > Original script is here: https://github.com/FreddieChopin/bleeding-edge-toolchain/blob/master/build-bleeding-edge-toolchain.sh. It is fairly straightforward. What I am running into now, is that when producing gcc and newlib-cygwin-nano, I do not generate all expected targets: This uses --with-multilib-list=rmprofile which gives a large multilib list for cortext r and m parts. It appears that you aren't using this, and hence getting the default multilib list which is smaller. > Searching for librdimon.a was done as it is produced for the C++ target. Are the actions undertaken in `copyNanoLibraries` (https://github.com/FreddieChopin/bleeding-edge-toolchain/blob/master/build-bleeding-edge-toolchain.sh#L584) not part of the build process elsewhere? This is not part of the standard build process, and you need to do this manually in your build script. You are building newlib twice, and then renaming files so you can combine two newlib builds into one newlib install tree. Jim
