public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: George Hodgkins via Libc-help <libc-help@sourceware.org>
Cc: George Hodgkins <hodgkinsgeorge@gmail.com>
Subject: Re: Diagnosing symbol conflicts in modified glibc build
Date: Mon, 28 Jun 2021 21:53:47 +0200	[thread overview]
Message-ID: <87bl7prcj8.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CA+U-Cbz9zgXP0dOSzK4qMr2_3NftG9kLmQFG5LUX0uOpqdnfEw@mail.gmail.com> (George Hodgkins via Libc-help's message of "Mon, 28 Jun 2021 13:42:52 -0600")

* George Hodgkins via Libc-help:

> Unfortunately, that doesn't seem to resolve the issue. There are actually
> parts of our code that need to be linked into the loader, but as an
> experiment I tried wrapping all of our code in the macros you suggested.
> The same errors occurred.

Then you'll have to use the link editor's tracing capabilities (map
files, the -y option, etc.) to figure out what is pulling the multiple
definitions.

Thanks,
Florian


      reply	other threads:[~2021-06-28 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 20:03 George Hodgkins
2021-06-23 20:35 ` Florian Weimer
2021-06-28 19:42   ` George Hodgkins
2021-06-28 19:53     ` Florian Weimer [this message]

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=87bl7prcj8.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=hodgkinsgeorge@gmail.com \
    --cc=libc-help@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).