Suraj Kumar commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/29#note_111317 I think the issue is that on fresh builds, it does not seem to be able to run `sparc-rtems6-gcc`, hence the odd string that `sed` is trying to replace with. That seems to be the one causing the issue here. Also, the script install location does not exist yet, since the RSB only writes at the end of the build - I have fixed this issue. @chris For cases like this (where `sparc-rtems6-gcc` is not yet built, can a fall back option be to use the `gcc_version` macro defined in the corresponding `newlib` file for that build? Please let me know, thanks @amar After I had moved files around, I had only re-built current toolchains I already had built, I had forgotten to re-test for this case. That is my bad and this will be fixed ASAP -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/29#note_111317 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
