From: hjl@lucon.org (H.J. Lu)
To: rth@cygnus.com
Cc: mdorman@law.miami.edu, egcs@cygnus.com
Subject: Re: 1.0.3 pre-release available
Date: Mon, 27 Apr 1998 08:47:00 -0000 [thread overview]
Message-ID: <m0yTpwJ-000598C@ocean.lucon.org> (raw)
In-Reply-To: <19980426221550.20521@dot.cygnus.com>
>
> I don't recall what the tstring.cc failure is. I'm much worse about
> following up on c++ failures vs c/f77 failures.
>
I think that may be caused by the new binutils and old glibc. At
least, that was what I saw on alpha. Please make sure you follow
my release note if you use binutils newer than 2.8.1. I don't think
the official binutils mentions it at all.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-04-27 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-26 0:01 Jeffrey A Law
1998-04-26 8:21 ` Toon Moene
1998-04-26 10:05 ` Jeffrey A Law
1998-04-26 18:03 ` Michael Alan Dorman
1998-04-27 0:33 ` Richard Henderson
1998-04-27 8:47 ` H.J. Lu [this message]
1998-04-26 12:45 ` H.J. Lu
1998-04-26 10:05 ` Jeffrey A Law
[not found] ` <m0yTUQG-000598C.cygnus.egcs@ocean.lucon.org>
1998-04-26 21:56 ` Nathan Myers
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=m0yTpwJ-000598C@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=mdorman@law.miami.edu \
--cc=rth@cygnus.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).