On Fri, Jan 31, 2025 at 2:11 PM Robert W <rbt...@gmail.com> wrote: > > This sounds like you might be using the BSP build sets in the RSB. It > might > > be better for you to build just the tools with the bset 6/rtems-m68k and > then > > build and test BSPs individually. That way you can test, tweak, debug, > test, > > etc each BSP without having to rebuild the tools. > > > > The tools do not need to change between builds of BSPs within the same > > architecture which is why the BSP bsets are good for production > deployment > > but can be awkward for testing. > > > > --joel > > > > From " > https://ftp.rtems.org/pub/rtems/releases/5/5.3/#quick-guide-to-building"; > > " > . > . > . > To build the tools for the ARM architecture: > > ../source-builder/sb-set-builder \ > --prefix=$HOME/development/rtems/5.3 \ > 5/rtems-arm > " > > This *exact* ( used this line out of the manual for this target) line > fails with: > > " > . > . > > building: expat-2.1.0-x86_64-linux-gnu-1 > sizes: expat-2.1.0-x86_64-linux-gnu-1: 7.459MB (installed: 1.417MB) > cleaning: expat-2.1.0-x86_64-linux-gnu-1 > reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.txt > reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.xml > config: tools/rtems-gdb-9.1-1.cfg > error: shell macro failed: > > /usr/local/packages/ee/rtems/rtems.20250125.2015.rtems52/rtems-source-builder-5.2/source-builder/sb/rtems-build-dep > -c gcc -l : 2: error: no library (-l) provided > Build FAILED > Build Set: Time 0:00:23.866886 > Build FAILED > " > **Please note that this sequence successfully builds "automake" and > "autoconf" before encountering the error building gdb > > Is this not the right way to build the tools? > I'm not able to find any other instructions for building compiler tools. >
I am pretty sure 5.3 is still referencing URLs that do not exist since we switched to Gitlab. The 5 branches should be OK. We are discussing cutting a 5.4 but it was second to getting 6.1 out. 6.1 is out and would be a better starting point. Also you can add --log=FILE and maybe even --trace to see what was tried but it looks like it didn't find a library it needed (no idea which or why) and the name on the -l argument expanded to nothing. --joel > > Help appreciated, Thanks. > > Robert W. >
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
