public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: <sellcey@imgtec.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Build problem with ToT GCC
Date: Fri, 17 Apr 2015 19:58:00 -0000	[thread overview]
Message-ID: <20150417195820.664E52C3B86@topped-with-meat.com> (raw)
In-Reply-To: Steve Ellcey's message of  Friday, 17 April 2015 12:51:52 -0700 <1429300312.30498.241.camel@ubuntu-sellcey>

> This patch did fix the problem in dl-open.c but dl-close.c has the same
> issue and would need the same fix.

Please show that error.

  reply	other threads:[~2015-04-17 19:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 18:08 Steve Ellcey 
2015-04-17 19:20 ` Roland McGrath
2015-04-17 19:51   ` Steve Ellcey
2015-04-17 19:58     ` Roland McGrath [this message]
2015-04-17 20:02       ` Steve Ellcey
2015-04-17 20:46         ` Steve Ellcey
2015-04-17 21:03           ` [COMMITTED PATCH] Fuller check for invalid NSID in _dl_open Roland McGrath
2015-04-17 21:31           ` Build problem with ToT GCC Roland McGrath
2015-04-17 21:52             ` Steve Ellcey
2015-04-17 22:01               ` 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=20150417195820.664E52C3B86@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sellcey@imgtec.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).