From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: PROVIDE problems
Date: Sun, 27 Apr 2003 18:31:00 -0000 [thread overview]
Message-ID: <200304271831.h3RIVuf13768@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Sunday, 27 April 2003 01:18:53 -0700 <3EAB926D.9020408@redhat.com>
> I had problems with Roland's change to the linker script generation.
> Adding PROVIDE to define __start___libc_freeres_ptrs etc didn't work for
> some reason. I've removed the PROVIDEs now. This means we have a few
> more symbols where they don't belong but it's better than nothing. This
> might be a linker bug but I'm not sure about this at this point.
What broken results did you see? It looked ok to me. The linker produces
the symbols as undefined locals in the libc.so .symtab, which is odd.
But it uses the right values in the GOT, where it matters.
next prev parent reply other threads:[~2003-04-27 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 8:19 Ulrich Drepper
2003-04-27 18:31 ` Roland McGrath [this message]
2003-04-27 18:38 ` Ulrich Drepper
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=200304271831.h3RIVuf13768@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).