Software > Firmware
Blackbird firmware build fails on Blackbird
manatails:
When building system firmware v2.00 for Blackbird I am getting the following error as seen in the screenshot.
I used the commands from the wiki page: https://wiki.raptorcs.com/wiki/Compiling_Firmware
and the same build finishes successfully on another amd64 system.
Can somebody confirm this?
Both systems run Debian buster.
madscientist159:
So you're saying it's only failing on a ppc64le host? Can you post the full output log?
We use Debian Stretch to build the firmware (on POWER) internally, as IBM hasn't really tested newer versions of some of the underlying software (the XML libraries are a particular problem, as is Perl).
manatails:
Yes, the build only fails on ppc64le system, and attached is the full build log file.
madscientist159:
Can you post the build log from a full clean build? This one looks like it was restarted, and from the error messages I'm guessing the toolchain didn't compile correctly.
The fastest way to make this work for sure is to install a Debian Stretch chroot, bind mount /proc, /sys, and /dev, then build inside that chroot. I don't think IBM fully supports the newer software versions in Buster, and from the log I can't (yet) determine why it'd fail on POWER other than it's possible the native compile path is different and somehow broken on Buster.
I'd like to see this fixed, but I'm not 100% sure when I'd have time to get a new environment set up and test build, which is why I'd like to see the full log from scratch build. Maybe it's something simple (missing package?) :)
manatails:
--- Quote from: madscientist159 on May 14, 2020, 02:00:02 pm ---Can you post the build log from a full clean build? This one looks like it was restarted, and from the error messages I'm guessing the toolchain didn't compile correctly.
The fastest way to make this work for sure is to install a Debian Stretch chroot, bind mount /proc, /sys, and /dev, then build inside that chroot. I don't think IBM fully supports the newer software versions in Buster, and from the log I can't (yet) determine why it'd fail on POWER other than it's possible the native compile path is different and somehow broken on Buster.
I'd like to see this fixed, but I'm not 100% sure when I'd have time to get a new environment set up and test build, which is why I'd like to see the full log from scratch build. Maybe it's something simple (missing package?) :)
--- End quote ---
I got the full log file but as it exceeds the attachment file size limit I temporarily uploaded it onto my server.
Here it is: http://3.1.2.2/temp/fullbuild.log
Navigation
[0] Message Index
[#] Next page
Go to full version