On 4/10/21 3:06 am, Joel Sherrill wrote: > No BSP was successfully built in the build sweep Friday. All have > failures like this: > > $ ./waf bsp_defaults --rtems-bsps=powerpc/psim > There is no top-level group with UID '/grp' in the specification > > The script fetches the BSP's defaults and then changes settings for > enable tests, etc. > > Anyone else see this?
I would not use the the bsp_defaults approach to handle BSP testing. The BSP defaults build target should only be used as a means to find and examine any options a BSP may have you wish to override. Capturing defaults is counter to the notion of defaults, ie defaults change? If you wish to use the defaults then this is all you need: $ echo "[powerpc/psim]" > config $ ./waf distclean configure build If you what to build the tests, POSIX API and debug on: $ echo "[powerpc/psim]" > config $ echo "RTEMS_DEBUG = True" >> config $ echo "RTEMS_POSIX_API = True" >> config $ echo "BUILD_TESTS = True" >> config $ ./waf distclean configure build In regards to removing build directories and others things in the lengthy thread attached to the email, user beware. The recommended solution is: ./waf distclean Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
