From: caiyinyu Date: Tue, 28 Mar 2023 01:19:53 +0000 (+0800) Subject: LoongArch: ldconfig: Add comments for using EF_LARCH_OBJABI_V1 X-Git-Tag: glibc-2.38~461 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=07dd75589ecbedec5162a5645d57f8bd093a45db;p=thirdparty%2Fglibc.git LoongArch: ldconfig: Add comments for using EF_LARCH_OBJABI_V1 We added Adhemerval Zanella's comment to explain the reason for using EF_LARCH_OBJABI_V1. --- diff --git a/sysdeps/unix/sysv/linux/loongarch/readelflib.c b/sysdeps/unix/sysv/linux/loongarch/readelflib.c index ceba3559595..e34612895d2 100644 --- a/sysdeps/unix/sysv/linux/loongarch/readelflib.c +++ b/sysdeps/unix/sysv/linux/loongarch/readelflib.c @@ -40,6 +40,12 @@ process_elf_file (const char *file_name, const char *lib, int *flag, ret = process_elf64_file (file_name, lib, flag, isa_level, soname, file_contents, file_length); + + /* The EF_LARCH_OBJABI_V1 flag indicate which set of static relocations + the object might use and it only considered during static linking, + it does not reflect in runtime relocations. However some binutils + version might set it on dynamic shared object, so clear it to avoid + see the SO as unsupported. */ flags = elf64_header->e_flags & ~EF_LARCH_OBJABI_V1; /* LoongArch linkers encode the floating point ABI as part of the ELF headers. */