cc: internal compiler error: Segmentation fault signal terminated program cc1

While building an application with corteca build, randomly we receive the following error:

...

14.54 cc -Werror -Wall -Wextra -Wformat=2 -Wshadow -Wwrite-strings -Wredundant-decls -Wpedantic -Wmissing-declarations -Wno-format-nonliteral -fPIC -g3 -I ../include -I ../include_priv -Wstrict-prototypes -Wold-style-definition -Wnested-externs -Wdeclaration-after-statement -std=c11 -c -o ../output/aarch64-alpine-linux-musl/amxc_string.o amxc_string.c
15.70 cc: internal compiler error: Segmentation fault signal terminated program cc1
15.70 Please submit a full bug report, with preprocessed source (by using -freport-bug).
15.70 See <https://gitlab.alpinelinux.org/alpine/aports/-/issues> for instructions.
15.70 make[1]: *** [makefile:62: ../output/aarch64-alpine-linux-musl/amxc_string.o] Error 4
15.70 make[1]: Leaving directory '/Ambiorix/libamxc/src'
15.71 make: *** [makefile:23: all] Error 2
...

The workaround I have found is to run the following command:

sudo sysctl -w kernel.randomize_va_space=0

This command is from a related issue of buildx, which is used internally by corteca.
Related issue: https://github.com/docker/buildx/issues/3170

Start by reproducing the failure with corteca build, then inspect how its internal Docker buildx invocation reaches makefile:62 while compiling src/amxc_string.c. Compare the behavior with the linked buildx issue and the kernel.randomize_va_space=0 workaround; done means identifying whether corteca can resolve the crash or documenting that the fault is external.