From: hjl@lucon.org (H.J. Lu)
To: manfred@s-direktnet.de
Cc: kenner@vlsi1.ultra.nyu.edu, eggert@twinsun.com,
drepper@cygnus.com, hjl@lucon.org, gcc2@cygnus.com,
egcs@cygnus.com
Subject: Re: libstdc++-2.8.1 - Ready for testing
Date: Fri, 20 Feb 1998 12:26:00 -0000 [thread overview]
Message-ID: <m0y5wBy-00058KC@ocean.lucon.org> (raw)
In-Reply-To: <199802201640.RAA00917@saturn.s-direktnet.de>
>
> I've created a new distribution which should be released with the next
> gcc-2.8.1 release.
>
> I took libstdc++-2.8.0 as the basis, added the most important changes
> from the upcoming egcs-1.0.2 release (mostly fixes for glibc2 on
> Linux), and added two new files (INSTALL and texinfo/lgpl.texinfo).
>
> Diffs from libstdc++-2.8.0 are available; file info:
>
> 34372 Feb 20 17:24 libstdc++-2.8.0-2.8.1-980220.diff.gz
> 831351 Feb 20 17:35 libstdc++-2.8.1-980220.tar.gz
>
> If you are interested, I'd like to upload them onto an ftp server and
> to invite you to test them before gcc-2.8.1 will be released; if yes,
> please tell me what ftp server, directory and user account I should
> use.
>
> BTW, I tested them on sparc-sun-solaris2.5.1 and sparc-sun-sunos4.1.4
> without problems.
>
Could you please wait for a while after we settle down on thread-safe
under glibc 2? Also it would be nice to have my libg++ patch to
configure/configure.in.
Thanks.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-02-20 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-20 10:10 Manfred Hollstein
1998-02-20 12:26 ` H.J. Lu [this message]
1998-02-20 12:26 ` Manfred Hollstein
1998-02-21 9:51 ` Manfred Hollstein
1998-02-21 15:27 ` H.J. Lu
1998-02-22 3:20 ` Manfred Hollstein
1998-02-22 3:22 ` Manfred Hollstein
1998-02-23 11:00 ` H.J. Lu
1998-02-23 13:07 ` Manfred Hollstein
1998-02-23 11:54 ` Ulrich Drepper
1998-02-22 4:57 ` Andi Kleen
1998-02-22 8:37 ` Manfred Hollstein
[not found] <9802202130.AA05758@vlsi1.ultra.nyu.edu>
1998-02-21 14:20 ` Manfred Hollstein
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=m0y5wBy-00058KC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=eggert@twinsun.com \
--cc=gcc2@cygnus.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=manfred@s-direktnet.de \
/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).