On Mon, Nov 25, 2019 at 8:40 PM Adhemerval Zanella <adhemerval.zane...@linaro.org> wrote: > > > > On 25/11/2019 17:28, Andrew Dean via gcc wrote: > >>> This completes successfully. However, when I then try to run the gcc > >>> tests like > >> so: > >>> runtest --outdir . --tool gcc --srcdir /path/to/gcc/gcc/testsuite > >>> aarch64.exp --target aarch64-linux-gnu --target_board aarch64-sim > >>> --tool_exec > >>> /path_to/build_dir/install/compilers/aarch64-linux-gnu/bin/aarch64-gli > >>> bc-linux-gnu-gcc --verbose -v > >>> > >>> I get errors like this: > >>> > >>> aarch64-glibc-linux-gnu-gcc: fatal error: cannot read spec file > >>> 'rdimon.specs': No such file or directory > >>> > >>> I can see that the rdimon.specs flag is added based on this line in > >>> aarch64- > >> sim.exp: > >> > >> Where does aarch64-sim.exp comes from? > > > > /usr/share/dejagnu/baseboards/aarch64-sim.exp > > > >> > >>> > >>> set_board_info ldflags "[libgloss_link_flags] [newlib_link_flags] - > >> specs=rdimon.specs" > >>> > >> I think this is for baremetal/newlib targets, ie. aarch64-elf, not for > >> aarch64- > >> linux-gnu. > >
Yes -specs=rdimon.specs and other such flags are for use only on bare-metal targets. > > Hmm.. build-many-glibcs.py doesn't like either aarch64-elf or > > aarch64-linux-elf... > > I get a KeyError in build_compilers and build_glibcs when it tries to look > > up the config with either of those values. > > > > Unfortunately the build-many-glibcs.py does not have support for baremetal > build yet (since it is a tool created to build cross-compiling toolchain > using glibc). And glibc doesn't work bare-metal ...... regards Ramana
