Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/144#note_135844 Simple mistakes happen and at any level of the software stack and that is why I suggest auditing the final executable. A BSP developer can also check they have things sorted. Once a multilib variant is supported by GCC it is the BSP author that selects that variant and sets the ABI to match. This burnt into the BSP build data and is set and repeatable. Nothing needs to be configured. If users build third party packages they need to make sure the ABI matches and this depends on the type of build system integration they use. We export the ABI flags in `.pc` file as `ABI_FLAGS` so it is clear. In `Makefile.inc` they are called `CPU_CFLAGS`. The `rtems_waf` build support package uses the `.pc` ABI flags. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/144#note_135844 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
