public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Roland McGrath <roland@hack.frob.com>,
	<libc-alpha@sourceware.org>, <libc-ports@sourceware.org>
Subject: Re: Fix SHLIB_COMPAT with undefined obsoleting version
Date: Mon, 11 Mar 2013 14:38:00 -0000	[thread overview]
Message-ID: <mvm7gleq9x7.fsf@hawking.suse.de> (raw)
In-Reply-To: <513DE784.2020504@tilera.com> (Chris Metcalf's message of "Mon,	11 Mar 2013 10:17:40 -0400")

Chris Metcalf <cmetcalf@tilera.com> writes:

> What was confusing is that we appear to build pthread_atfork.os and
> then we don't use it.

That's a bug, it shouldn't even be built.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2013-03-11 14:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mvmr4juw5y8.fsf@hawking.suse.de>
     [not found] ` <20130308215906.6B7A22C0A5@topped-with-meat.com>
2013-03-11  9:46   ` Andreas Schwab
2013-03-11 13:09     ` Chris Metcalf
2013-03-11 13:36       ` Andreas Schwab
2013-03-11 14:17         ` Chris Metcalf
2013-03-11 14:38           ` Andreas Schwab [this message]
2013-03-12  9:18             ` [PATCH] Don't build .os objects of static-only-routines for extra libs Andreas Schwab
2013-03-12 14:06               ` Carlos O'Donell
2013-03-12 15:40                 ` Andreas Schwab
2013-03-12 22:24                   ` Carlos O'Donell
2013-03-12 14:23               ` Chris Metcalf
2013-03-12 17:38               ` Roland McGrath

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=mvm7gleq9x7.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=cmetcalf@tilera.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=roland@hack.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).