New issue by BikyAlex on void-packages repository

https://github.com/void-linux/void-packages/issues/35352

Description:
### System
Void Linux glibc aarch64 - Raspberry Pi 4

* xuname:  
  Void 5.10.52_1 aarch64 Unknown uptodate rF
* package:  
  *affected package(s) including the version*: ``LibreOffice 7.2.3.2 template from void-packages/srcpkgs ``

### Expected behavior
  compile successfully

### Actual behavior
  fail to compile

### Steps to reproduce the behavior
```
  cd void-packages
  git pull --rebase upstream master
  ./xbps-src binary-bootstrap
  ./xbps-src pkg libreoffice  
```

### Output:
```
[build RDB] services
[build PKG] svx_gengal
[build CXX] svx/source/gengal/gengal.cxx
[build LNK] Executable/gengal.bin
[build GAL] backgrounds
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'
make[1]: *** [/builddir/libreoffice-7.2.3.2/solenv/gbuild/Gallery.mk:56: /builddir/libreoffice-7.2.3.2/workdir/Gallery/backgrounds.done] Error 1
make: *** [Makefile:287: build] Error 2
=> ERROR: libreoffice-7.2.3.2_2: do_build: 'make ${makejobs} ${make_build_target}' exited with 2
=> ERROR:   in do_build() at srcpkgs/libreoffice/template:523
```


---

My question would be, where is "${makejobs}" defined in the template, because it only appears twice and in neither cases is it declared, unless xbps-src has this as an env variable somewhere. "${make_build_target}" is defined though. 

I did clean the hostdir/builddir folder once after the first failure, but that didn't seem to help. 

As a background, if that interests anyone, I'm using the Raspberry Pi 4 as my main PC (been my main for more than 8 months now), but libreoffice is not present in the aarch64 repo. I am assuming that's because libreoffice doesn't work with cross-compilation, so I have to compile it myself natively. I don't mind that, but I can't decode the xbps-src template myself and fix it. Does it work to compile on x86? I don't have an x86 system to test the template there. And I also cannot decode how buildbot works, so I can check the status of LO.