Hi everyone, just jumping back into RTEMS after using it on a Coldfire project in the late 90’s. As I used source builder it errored out because in my environment, per best practices, I don’t have a /bin/python. I have /bin/python3 and /bin/python2. This is considered best practice because it can be non-intuitive to know which version to use. That said, to get the source-builder to work, I added a symlink to python3 and it worked flawlessly. I’d suggest that all the scripts change /bin/env python to /bin/env python3 to help folks know that it’s python3 they want to use those scripts.
Which version of RTEMS are you using? This was changed a year ago in RTEMS and is slated for the next release. If it was RTEMS 7 (main) which program?
1 Like
Interesting, I was going to say ‘current’ because I just git cloned the repo and grabbed source _builder and built it, but because I was reading the online documentation I grabbed source_builder_6.2 which, true to its name, builds RTEMS 6.2 
On the plus side, I screwed up the PREFIX and ended up putting the tools in the repostority rather than my build path so looks like I’m gonna nuke the whole thing and start over. Nice to know that it has been fixed in main. Thanks for the quick reply!
1 Like