public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [Bug binutils/30281] error: multiple definition of `pwrite@GLIBC_2.2'; on i586-linux-gnu
Date: Wed, 29 Mar 2023 09:43:07 -0700	[thread overview]
Message-ID: <62d98d2e-05a9-0d84-3a1b-36a2b80388be@oracle.com> (raw)
In-Reply-To: <bug-30281-10543-Y4pxwK86oR@http.sourceware.org/bugzilla/>



On 3/29/23 05:24, mliska at suse dot cz wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=30281
>
> Martin Liska <mliska at suse dot cz> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |hjl.tools at gmail dot com
>             Assignee|vladimir.mezentsev at oracle dot c |unassigned at sourceware dot org
>                     |om                          |
>               Status|ASSIGNED                    |NEW
>            Component|gprofng                     |binutils
>
> --- Comment #3 from Martin Liska <mliska at suse dot cz> ---
> Great, thank you Vladimir. I was able to isolate that and reduce it. It started
> with 20ea3acc727f3be6322dfbd881e506873535231d and it's regression since
> 20ea3acc727f3be6322dfbd881e506873535231d.
>
> $ cat iotrace.i
> extern __inline __attribute__((__gnu_inline__)) void open64(int, ...) {}
> int __attribute__((__symver__("open64@GLIBC_2.2"))) __collector_open64_2_2() {}
> void open64(int, ...) {}
>
> $ cat libgprofng.ver
> GLIBC_2.2 {
>    global:
>      open64;
> };
>
> $ gcc iotrace.i -shared -fPIC -O2 -Wl,--version-script,libgprofng.ver
> -flto-partition=max -flto=auto -B ~/Programming/binutils/objdir/ld -fuse-ld=bfd
> /usr/bin/ld.bfd: /tmp/ccLS2iVj.ltrans1.ltrans.o: in function `open64':
> <artificial>:(.text+0x0): multiple definition of `open64@GLIBC_2.2';
> /tmp/ccLS2iVj.ltrans0.ltrans.o:<artificial>:(.text+0x0): first defined here
> collect2: error: ld returned 1 exit status
>
> while -fuse-ld=mold or -fuse-ld=lld works fine. gold is also affected.
>
> @H.J. Can you please take a look?
>

  How do you configure a build to set  -fuse-ld=lld ?

On Ol9, a build is configured with the -flto option. How can I turn it 
off ?

Thank you,
-Vladimir



       reply	other threads:[~2023-03-29 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-30281-10543@http.sourceware.org/bugzilla/>
     [not found] ` <bug-30281-10543-Y4pxwK86oR@http.sourceware.org/bugzilla/>
2023-03-29 16:43   ` Vladimir Mezentsev [this message]
2023-03-31  7:18     ` Martin Liška

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62d98d2e-05a9-0d84-3a1b-36a2b80388be@oracle.com \
    --to=vladimir.mezentsev@oracle.com \
    --cc=binutils@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).