Hi @mcrajah,
That’s great you were able to figure it out!! The path to libgcc is determined using gcc’s -print-libgcc-file-name command option described here in the article. It sounds like for your setup that may be what was failing.
Do note that the arm-none-eabi package available via pacman is not an officially supported release of ARM gcc and is usually a version ahead of the official ARM release. While it can be interesting to use that build to pre-test new compiler releases, there’s usually configuration issues and new errors that arise as a result. For projects, I’d recommend using one of the official releases available here instead.