public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred Hollstein <manfred@s-direktnet.de>
To: hjl@lucon.org
Cc: kenner@vlsi1.ultra.nyu.edu, eggert@twinsun.com,
	drepper@cygnus.com, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: libstdc++-2.8.1 - Ready for testing
Date: Sun, 22 Feb 1998 03:22:00 -0000	[thread overview]
Message-ID: <199802221029.LAA00991@saturn.s-direktnet.de> (raw)
In-Reply-To: <199802220953.KAA00641@saturn.s-direktnet.de>

On Sun, 22 February 1998, 10:53:00, manfred@s-direktnet.de wrote:

 > On Sat, 21 February 1998, 14:17:14, hjl@lucon.org wrote:
 > 
 >  > > H.J., how many patches do you expect to get a `nearly final' libstdc++.
 >  > 
 >  > It should be very close. Does it work with "make check" for gcc 2.8.1?
 >  > libio/libstdc++ in egcs is fixed. I have sent 2 patches for egcs 1.0.2.
 >  > They should be included also if they aren't.
 >  > 
 >  > > 
 >  > > to my new libstdc++-2.8.1-980221. Since this shouldn't be tested on
 >  > > glibc2 systems only, I'd really prefer to upload them to Kenner's
 >  > > ftp server real soon now (especially because I expect a rather lengthy
 >  > > e-mail discussion afterwards - read the new INSTALL file and you will
 >  > > see what I mean ;-).
 >  > > 
 >  > 
 >  > I have tested libstdc++ from the latest egcs 1.0.2 with gcc 2.8.1 on
 >  > linux/x86 libc5 and linux/x86 glibc 2. They are ok with my patches.
 >  > Here are the list of files I changed:
 >  > 
 >  > ./configure
 >  > ./configure.in
 >  > ./libio/configure.in
 >  > ./libio/tests/Makefile.in
 >  > ./libio/tests/configure.in
 >  > ./libstdc++/configure.in
 >  > ./libstdc++/tests/configure.in
 >  > 
 > 
 > Good, just (Sun Feb 22 10:50:47 MET 1998) compared my CVS dir with the
 > one at Cygnus, no diffs - hence your changes should all be in the
 > libstdc++-2.8.1-980221 I uploaded yesterday to

Of course, they were not :-( Your patches for make check with gcc dir missing
were not in. I'm just uploading a new version libstdc++-2.8.1-980222 and will
delete yesterday's one. Sorry for the confusion.

Soon you'll will find on < ftp://jim.ultra.nyu.edu/pub/kenner/lc >:

-rw-r--r--   1 manfred  users       36797 Feb 22 11:23 libstdc++-2.8.0-2.8.1-980222.diff.gz
-rw-r--r--   1 manfred  users      831952 Feb 22 11:24 libstdc++-2.8.1-980222.tar.gz

Manfred

  reply	other threads:[~1998-02-22  3:22 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
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 [this message]
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=199802221029.LAA00991@saturn.s-direktnet.de \
    --to=manfred@s-direktnet.de \
    --cc=drepper@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=eggert@twinsun.com \
    --cc=gcc2@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).