Joel Sherrill commented: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/work_items/218#note_162162 There are multiple projects included by an RSB build of "RTEMS tools". Whether the executables are able to be moved to a new directory (e.g. prefix) after being built varies. Per Google on some of these: * GCC executables can be moved * Binutils executables cannot be moved * GDB executables can be moved * RTEMS cannot be moved (.pc file is a known issue) * Qemu is said to be movable but we have a dynamic library path with the prefix included in the build (--rpath). I do not think our build is movable. No idea on other tools we include like sis, dtc, and spike. This isn't something we have done wrong. It is something we inherit. If you know how to address every package we use and ensure it can be moved after installation, those changes would have to go through the upstream project. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/work_items/218#note_162162 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/14/sent_notifications/6-87utuq08q3qkyvxtf0ir2zrbe-e/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
