Chris Johns commented: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/21#note_126330 RTEMS's `waf` build system has decided to use `rtems-syms` to generate a C file and build it directly. This is counter to the design of `rtems-syms` as it is a tool to create an object file with symbols. I have no idea why that path was chosen and it makes this repo's support of loadable symbol tables fragile. The fact a C file is used internally and it could be optionally saved is an implementation detail and it that change if a different method is used to create the symbol table. The `rtems-syms` tool strips warnings from any supplied C flags when creating a symbol table as an object file. This was done to avoid this sort of noise. Having said this the change on branch and now in the MR (https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/64) silences the warnings. I believe the original #pragma solution was valid in this case. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/21#note_126330 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
