What does this source compile error at the end mean?

I’m compiling Zeek from Source on Debian going through all the steps, but at the end of ‘make’, I get the following err:

[ 89%] Built target bro_probabilistic
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
[ 89%] Built target bro_session
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
[ 89%] Built target bif_loader_plugins
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
[ 89%] Built target bif_loader
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
[100%] Built target zeek_objs
make[3]: Entering directory '/root/zeek-5.0.2/build'
make[3]: Leaving directory '/root/zeek-5.0.2/build'
make[3]: Entering directory '/root/zeek-5.0.2/build'
[100%] Linking CXX executable zeek
/usr/lib/aarch64-linux-gnu/libresolv.a(res_comp.o): in function `__res_hnok':
(.text+0x120): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `__stack_chk_guard@@GLIBC_2.17' defined in .data.rel.ro section in /lib/ld-linux-aarch64.so.1
/usr/bin/ld: (.text+0x120): warning: too many GOT entries for -fpic, please recompile with -fPIC
collect2: error: ld returned 1 exit status
make[3]: *** [src/CMakeFiles/zeek.dir/build.make:1603: src/zeek] Error 1
make[3]: Leaving directory '/root/zeek-5.0.2/build'
make[2]: *** [CMakeFiles/Makefile2:6797: src/CMakeFiles/zeek.dir/all] Error 2
make[2]: Leaving directory '/root/zeek-5.0.2/build'
make[1]: *** [Makefile:182: all] Error 2
make[1]: Leaving directory '/root/zeek-5.0.2/build'
make: *** [Makefile:15: all] Error 2

Specs:
OS: |Description:|Debian GNU/Linux 11 (bullseye)|
System: Raspberry Pi 4B 4Gb RAM

Works fine on my other Pi 4B instance with more RAM

This looks like a size limitation that is triggered on the architecture. I am not sure why this would work when using more ram though…