Alright I got the XML depedencies installed, I also had to install a static zlib to get it compiling. I misremembered the build failing with bitbake URLs earlier, it was actually buildroot that's failing to fetch stuff.
--2025-02-27 22:50:28-- http://sources.buildroot.net/ppe42-gcc/ppe42-gcc-84a6a88e95d3b52cf4a6979a5ca47a12daa6ec49-br1.tar.gz
2 things I notice. That revision (
84a6a88e95d3b5) indicates you're building a v2.1 firmware or newer. The second thing I notice is ppe42-gcc should come come from one of raptor's gitlab repos, not from
sources.buildroot.net. Did you make local changes or fail to
git submodules update or switch revisions without clearing your `output/` folder? What does
git status show? Which git revision of are you on? Also I think buildroot is sensitive to environment variables; if you're not using `bash` as your shell, it might not work.
Basically I would only expect it to try to fetch from
sources.buildroot.net if the
PPE42_GCC_SITE variable were messed with, and I doubt you edited
openpower/package/ppe42-gcc/ppe42-gcc.mk and changed it. It seems something is just messed up in your build environment...
You don't have to check out my copy of raptor's firmware repo to do so, but I would recommend following my README instructions and using the
Dockerfile.stretch (for building raptor-v2.00 based pnor) and
Dockerfile.debian (for building raptor-v2.10 based pnor) which I added to my repo. I plan to update the wiki eventually (and probably add a page about using docker for the build environment). The page on troubleshooting/debugging hostboot could use some expansion as well.
Both bitbake and buildroot can be rather sensitive to the local environment. If you have conflicting environment variables (maybe using a shell other than bash) could cause it to do weird things. My docker files should behave the same as a properly set-up debian chroot, but since the Dockerfile acts as a script, the environment is always the same and resetting the environment is as simple as exiting and then running the specific `docker run` command again. At some point I'll probably get Fedora and Ubuntu based dockerfiles working
Recent Posts
