New comment by Javyre on void-packages repository https://github.com/void-linux/void-packages/issues/24240#issuecomment-677971846 Comment: I basically just looked at the arch packagebuild and the packaging notes on the gccjit website and I transcribed the parts of the gcc void template that were relevant to libgccjit and x86-64. I'm not sure whether libgccjit should have it's own package template or be yet another subpackage of gcc. I think the best choice would be to have it as a subpackage of gcc and add an extra `./configure` and `make` call in `do_configure()` and `do_build()` so that libgccjit could be built with `--enable-host-shared` and not the rest of the packages. @zenny Assuming you're familiar enough with shell scripts, I suggest just starting and `Ctrl-F`ing through the [manual](https://github.com/void-linux/void-packages/blob/master/Manual.md) whenever you're confused. (worked for me) Also, I updated the gist with a terrible (but working) template for gccemacs that I am not proud of. Worth noting: - I had to add `libgccjit.so.0 libgccjit-9.3.0_6` to `common/shlibs` to get my gccemacs to install since xbps couldn't find the provider of that `.so`. - I had to disable the `hooks/post-install/11-pkglint-elf-in-usrshare.sh` hook since gccemacs (at least for the time being) stores `eln` files in `/usr/share`. If I understand correctly, this was fine before since they would be `el` or `elc` files which are portable, but with native-comp, now those files are actual binaries. This would definitely need to be fixed and discussed with andrea or another gccemacs dev. (It is unclear from the mailing list what the `eln` search path is or where it is even defined)