Build error: ELF section name out of range

[br3eze]

Godot version

4.03, 4.1

System information

Linux Arch

Issue description

The same for GCC and LLVM

The second try after the error:

scons: done reading SConscript files. scons: Building targets ... [Initial build] Linking Static Library modules/libmodule_astcenc.linuxbsd.editor.x86_64.a ... [Initial build] Ranlib Library modules/libmodule_astcenc.linuxbsd.editor.x86_64.a ... [Initial build] ranlib: modules/libmodule_astcenc.linuxbsd.editor.x86_64.a: malformed archive

Steps to reproduce

Output: Building for platform "linuxbsd", architecture "x86_64", target "editor"

Minimal reproduction project

git clone --depth 1 https://github.com/godotengine/godot -b 4.0.3-stable or 4.1 branch

[Calinou]

This may be the result of corrupted files as a leftover. Try cleaning all build files, then build again: git clean -dfxi

Also, do you have ccache installed? Try clearing its cache.

[br3eze]

@Calinou Empty cache. Cleared repo. Same Is it a long story or can be fixed somehow?

UPDATE When compiling with scons platform=linuxbsd use_llvm=yes linker=lld only one error appeas (screenshot)

And then it ends with:

[br3eze]

Does anybody know ANY workaround for this? It ruins everything.. Please share.

[capnm]

Does anybody know ANY workaround for this? It ruins everything.. Please share.

Maybe it's some hardware issue (RAM, HD) :thinking:. Try building it on an external hard drive or disabling the scons cache .

Or clone the entire repo with

git clone https://github.com/godotengine/godot
git checkout origin/4.1 -b 4.1
git gc

etc...

[akien-mga]

Yes check that you're not running out of disk space in either your $HOME and the partition where you're compiling Godot.

If that's not disk space, then it sounds like memory corruption.

[Calinou]

I suggest running Memtest86+ on your machine for an hour or two to check if the RAM is faulty.

[br3eze]

• not disk space
• memtest86 showed green "passed"
• tried two ssd disks
• cache disabled

[br3eze]

At last, badblocks -Bvsno showed some issues on a brand new system (not a data with a project!) Samsung ssd! Can't say which files were involved, may be some libs. Thanks everybody!