While setting up RTEMS on macOS (Apple Silicon, macOS 15 Sequoia), I ran into a couple of issues that might be helpful for other macOS users.
First, the documentation mentions Python 3.12 when creating the virtual environment. I initially used Python 3.13, but rtems-test failed because telnetlib has been removed in Python 3.13. Switching to Python 3.12 fixed the issue.
I also ran into a problem with install-info. The build process expected /usr/bin/install-info, which wasn’t present on my system. Installing texinfo using Homebrew solved it:
brew install texinfo
After that the build completed successfully.
Just sharing this in case it helps someone else setting things up on newer macOS versions.
Thanks for the info. I am on Tahoe 26.3.1 and the latest Xcode and I can build the tools.
The supplied Python seems to be working:
chris@weka rtems % type python3
python3 is /Library/Frameworks/Python.framework/Versions/3.13/bin/python3
The telnetlib problem is in rtems-tools and is present on hosts so it is not MacOS specific.
I do not use brew and I keep my MacBook clear of MacPorts and Homebrew packages to make sure we build with just Xcode. I would prefer we avoid references to Homebrew and MacPorts in our documentation. This is not a reflection on those projects. If packages from those projects are on a system they can become part of the build expanding the possible reasons a build fails. The added complexity increases the time needed to maintain the support. These projects use a rolling release and that means the version of packages you have installed may be different to my versions so who’s versions is the right one? My simple solution after hitting a range of issues a long time ago was removing these 3rd party packages so I can deal with the upstream tools projects like gcc or Apple. I have raised a number of bug reports with Apple over the years.
If you have other brew tools installed, for example gcc it can change the build and that could make a dependence path requires more brew packages.
Thanks for the clarification. On my system the tools are building and running correctly now as well. The issue I ran into earlier was related to the Python environment during setup, but after adjusting that the build completed successfully.
I’ll continue experimenting with RTEMS and looking into Cobra analysis as part of my GSoC preparation.