PDA

View Full Version : ARM build scripts?



hinermad
2022-07-26, 21:34
Hello,

I've tried to build images for Raspberry Pi (32 and 64 bit) and Beaglebone Black (same) and every time I end up with errors like this:


/tmp/cchjW2EZ.s:74: Error: selected processor does not support `dmb ish' in ARM mode

The unsupported instructions vary, but the error message is the same.

I cloned the ARM build scripts from the kali-arm repo at Gitlab according to the docs. I've tried to build these on Kali VMs under VirtualBox and also on native installs on a Raspberry Pi 4. Both hosts yield the same errors.

Am I missing something? Is there a different package I need to install, or a configuration I need to change on an existing one?

Fred Sheehan
2022-08-01, 21:06
try some google-fu...

https://stackoverflow.com/questions/62304821/selected-processor-does-not-support-dmb-ish-in-arm-mode

hinermad
2022-08-08, 15:51
try some google-fu...

https://stackoverflow.com/questions/62304821/selected-processor-does-not-support-dmb-ish-in-arm-mode

I did search for some help, and I saw that post. I realize I need the compiler to build for the neon FPU but that article doesn't say anything about how to get the Kali build script to do it.

steev
2022-08-08, 22:01
How are you running the scripts? That seems like it's trying to use an arm64 (64-bit) compiler to build armhf (32-bit) which isn't going to work. The BBB script likely needs some work and is considered "community supported" but the Raspberry Pi scripts are all maintained, and they get built every day, as well as once a week.

hinermad
2022-08-09, 14:36
How are you running the scripts? That seems like it's trying to use an arm64 (64-bit) compiler to build armhf (32-bit) which isn't going to work. The BBB script likely needs some work and is considered "community supported" but the Raspberry Pi scripts are all maintained, and they get built every day, as well as once a week.

I got the same errors when I tried to use the Raspberry Pi script to build an image for a Pi 2, so whatever is causing it does seem to be common to the ARM tools. I ran both scripts on a Kali VM with the --arch armhf option.

I found a commit message for one of the scripts somewhere (which I can't find again, unfortunately) that said the later version of the ARM compiler (I think it was version 11 at the time) had changed how it recognized the FPU selection. (Or maybe the default selection?) I installed version 10 of the tools and made them the default on my VM and was able to build images for both the Pi 2 and (as of yesterday) the Beaglebone Black as well. So my question has been resolved.

Thanks!