Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/3671#note_121948 I am not sure about this issue and what is happening here. Where do the tools come from with a "different" release? Looking at the initial data posted my guess is a version 5 RSB was used to build a version 6 tools and then a version 5 kernel was used with the version 6 tool and finally a version 5 `rtems-tools` build is expected to work with this. I see a slippery of what a _version_ change means? Could the need for this change please be reviewed against the RSB and the recent changes to it to support `next`? I also suggest a review of the `rtems.git` build system `configure` be made and if a version option is present there? If it is present I would like to see it removed. Overriding a version when testing can be seem as simple however I think allowing a version to be overridden in a release is dangerous. We should look for better ways to manage _next_ revisions and I think the recent RSB approach looks a better way. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/3671#note_121948 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
