aboutsummaryrefslogtreecommitdiff
path: root/crypt/sha256-crypt.c
diff options
context:
space:
mode:
authorXi Ruoyao <xry111@xry111.site>2023-03-26 19:13:34 +0800
committercaiyinyu <caiyinyu@loongson.cn>2023-03-27 16:57:56 +0800
commit952b7630c72ae245f370f1a2bcaade82bb1f7361 (patch)
treed073e9370095c3fdd9336ba2fae9f880e4353020 /crypt/sha256-crypt.c
parent152f863926e77c6f9c9a8b8779c8084eb844ec44 (diff)
downloadglibc-952b7630c72ae245f370f1a2bcaade82bb1f7361.tar
glibc-952b7630c72ae245f370f1a2bcaade82bb1f7361.tar.gz
glibc-952b7630c72ae245f370f1a2bcaade82bb1f7361.tar.bz2
glibc-952b7630c72ae245f370f1a2bcaade82bb1f7361.zip
LoongArch: ldconfig: Ignore EF_LARCH_OBJABI_V1 in shared objects
Binutils 2.40 sets EF_LARCH_OBJABI_V1 for shared objects: $ ld --version | head -n1 GNU ld (GNU Binutils) 2.40 $ echo 'int dummy;' > dummy.c $ cc dummy.c -shared $ readelf -h a.out | grep Flags Flags: 0x43, DOUBLE-FLOAT, OBJ-v1 We need to ignore it in ldconfig or ldconfig will consider all shared objects linked by Binutils 2.40 "unsupported". Maybe we should stop setting EF_LARCH_OBJABI_V1 for shared objects, but Binutils 2.40 is already released and we cannot change it.
Diffstat (limited to 'crypt/sha256-crypt.c')
0 files changed, 0 insertions, 0 deletions