public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@frob.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: separately compiling libc modules for rtld
Date: Tue, 01 Oct 2002 01:26:00 -0000	[thread overview]
Message-ID: <20021001102645.Y3451@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <200210010825.g918P6E10682@magilla.sf.frob.com>; from roland@frob.com on Tue, Oct 01, 2002 at 01:25:06AM -0700

On Tue, Oct 01, 2002 at 01:25:06AM -0700, Roland McGrath wrote:
> > I know that Hurd has problems.  But exported symbols temporarily should
> > be able to fix that, right?  And it also doesn't introduce any permanent
> > ABI damage.  So I'd rather go this way unless you prefer to not change
> > the code and declare 2.3.1 as the first release usable for Hurd.
> 
> That would be ok with me, but it might be hard for the Debian/Hurd guys.
> 
> There is never any question of ABI breakage that I know of, just that it
> works or it doesn't or it has too many PLT entries and is less optimal.  
> It seems to me the simplest thing for now would be to make it easy to just
> disable all the hidden_proto stuff entirely and have Hurd do that.  
> I'll add something.

Yeah, I think a simple libc-symbols.h change is best for 2.3.

	Jakub

      reply	other threads:[~2002-10-01  8:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 23:45 Roland McGrath
2002-10-01  0:31 ` Ulrich Drepper
2002-10-01  1:25   ` Roland McGrath
2002-10-01  1:26     ` Jakub Jelinek [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=20021001102645.Y3451@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@frob.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).