[Bug binutils/30281] error: multiple definition of `pwrite@GLIBC_2.2' with LTO and symver attribute

[Vladimir Mezentsev]

Can someone from the ld team take a look at what happened.
I thought H.J. Lu made a fix for ld (see his comments in 
https://sourceware.org/bugzilla/show_bug.cgi?id=30281)


Thank you,
-Vladimir



-------- Forwarded Message --------
Subject: 	[Bug binutils/30281] error: multiple definition of 
`pwrite@GLIBC_2.2' with LTO and symver attribute
Date: 	Thu, 30 May 2024 02:53:42 +0000
From: 	usaonmonday at gmail dot com <sourceware-bugzilla@sourceware.org>
To: 	vladimir.mezentsev@oracle.com



https://sourceware.org/bugzilla/show_bug.cgi?id=30281

--- Comment #15 from Andrey Sotnikov <usaonmonday at gmail dot com> ---
$ ld --version
GNU gold (GNU Binutils 2.42.0.20240530) 1.16

Same result. The full ld's command line captured with strace:

/home/user/binutils-env/bin/ld -plugin
/home/user/gcc-env/lib/gcc/x86_64-linux-gnu/14/liblto_plugin.so
-plugin-opt=/home/user/gcc-env/lib/gcc/x86_64-linux-gnu/14/lto-wrapper
-plugin-opt=-fresolution=/tmp/cc1r18nR.res -plugin-opt=-pass-through=-lgcc
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s
--eh-frame-hdr -m elf_x86_64 -shared -o .libs/libgp-sync.so /lib/crti.o
/home/user/gcc-env/lib/gcc/x86_64-linux-gnu/14/crtbeginS.o
-L/home/user/gcc-env/lib/gcc/x86_64-linux-gnu/14 -L/lib -L/usr/lib
-L/home/user/gcc-env/lib -L/home/user/binutils-env/lib .libs/synctrace.o
--version-script ../../../binutils-gdb/gprofng/libcollector/libgprofng.ver
--no-as-needed -lrt -ldl -soname libgp-sync.so -lgcc --push-state 
--as-needed
-lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state
/home/user/gcc-env/lib/gcc/x86_64-linux-gnu/14/crtendS.o /lib/crtn.o

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/binutils/attachments/20240529/4f7cf18e/attachment-0001.htm>