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: Wed, 23 Jun 2021 22:35:48 +0200 [thread overview]
Message-ID: <87pmwcxqsb.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CA+U-CbyxhrCBy-tWbctqDchg3G-8CjwV94sWtPXTYZ_9kiwoAg@mail.gmail.com> (George Hodgkins via Libc-help's message of "Wed, 23 Jun 2021 14:03:05 -0600")
* George Hodgkins via Libc-help:
> With that extensive preamble, the actual problem we are facing is the
> failure of this command:
> #################
> cc -nostdlib -nostartfiles -r -o /glibc-wsp/build/elf/librtld.map.o
> -Wl,--defsym=calloc=0 -Wl,--defsym=free=0 -Wl,--defsym=malloc=0
> -Wl,--defsym=realloc=0 -Wl,--defsym=__stack_chk_fail=0
> -Wl,--defsym=__stack_chk_fail_local=0 \
> '-Wl,-(' /glibc-wsp/build/elf/dl-allobjs.os
> /glibc-wsp/build/libc_pic.a -lgcc '-Wl,-)'
> -Wl,-Map,/glibc-wsp/build/elf/librtld.mapT
> /glibc-wsp/build/libc_pic.a(getcwd.os): In function `__GI___getcwd':
> /glibc-wsp/src/io/../sysdeps/unix/sysv/linux/getcwd.c:47: multiple
> definition of `__getcwd'
> /glibc-wsp/build/elf/dl-allobjs.os:/glibc-wsp/src/elf/../sysdeps/unix/sysv/linux/getcwd.c:47:
> first defined here
This probably means that you are linking more into the dynamic loader
than you intend. You may have to cover your own additions with
#if IS_IN (libc) or #if !IS_IN (rtld).
Thanks,
Florian
next prev parent reply other threads:[~2021-06-23 20:35 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 [this message]
2021-06-28 19:42 ` George Hodgkins
2021-06-28 19:53 ` Florian Weimer
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=87pmwcxqsb.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).