There is nothing you as a user or contributor can do about this.

This package has grown too large to build on OBS. GCC has an aarch64-specific 
problem that it assumes a limit on text size while compiling _unless_ you build 
it with LTO. If you try to link a too large executable you get relocation 
overflows.

Thus it has to be built with LTO. But then the linking phase requires enormous 
amounts of memory (30ish GB in one process) and the OBS admins have refused to 
provide us with even one build VM with such a configuration. (I'm under the 
impression that entries under one header at https://build.opensuse.org/monitor 
represent multiple VMson the same host; if that's incorrect please correct me)

Reply via email to