From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Mike Stump <mrs@wrs.com>
Cc: egcs@cygnus.com
Subject: Re: gcc2 merge
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <36AF7591.9DE84056@moene.indiv.nluug.nl> (raw)
Message-ID: <19990131235800.UYlTc2gTwA-ipVuTY9Qob_KYA_SEg_bV9Ds_nS_ZIKU@z> (raw)
In-Reply-To: <199901271357.FAA00675@kankakee.wrs.com>
Mike Stump wrote:
> First problem, everyone be sure to cvs update with -d, things won't
> build without it! I hate to point this out, but I do in hopes of
> forestalling a small flood of why can't I build it anymore messages.
Thanks.
That seems to work over here -
[toon@moene toon]$ /usr/snp/bin/gcc -v
Reading specs from
/usr/snp/lib/gcc-lib/i686-pc-linux-gnu/egcs-2.93.03/specs
gcc version egcs-2.93.03 19990127 (gcc2 ss-980929 experimental)
I am now running the LAPACK test suite (assuming that there are enough
people with the above mentioned target who can run the regular test set
first) ~ crunch ~ crunch ~ crunch .... DONE.
Hmmm, I18N ...
Uw rekentuig heeft een onwettige opdracht uitgevoerd.
Wenst U hem:
1. De Blauwe Dood.
2. Een Schop tegen de Rode Knop.
3. Opnieuw tot leven te wekken met Drie Vingers.
Uw Keuze: _
--
Toon Moene (toon@moene.indiv.nluug.nl)
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Phone: +31 346 214290; Fax: +31 346 214286
g77 Support: fortran@gnu.org; egcs: egcs-bugs@cygnus.com
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-27 5:57 Mike Stump
1999-01-27 12:25 ` Toon Moene [this message]
1999-01-31 23:58 ` Toon Moene
1999-01-31 23:58 ` Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1999-09-06 2:12 Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-01-28 7:01 Kaveh R. Ghazi
1999-01-28 9:18 ` Jeffrey A Law
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Kaveh R. Ghazi
1999-01-27 5:44 Mike Stump
1999-01-31 23:58 ` Mike Stump
1999-01-27 1:50 Jeffrey A Law
1999-01-27 12:47 ` Andreas Jaeger
1999-01-27 13:10 ` Alexandre Oliva
1999-01-27 13:54 ` Andreas Jaeger
1999-01-31 23:58 ` Andreas Jaeger
1999-01-29 5:39 ` H.J. Lu
1999-01-29 5:49 ` Nick Burrett
1999-01-29 5:52 ` H.J. Lu
1999-01-29 5:59 ` Nick Burrett
1999-01-29 6:32 ` Matthew Kirkwood
1999-01-29 7:54 ` Jean-Pierre Radley
1999-01-29 6:35 ` Zack Weinberg
1999-01-29 10:49 ` Jeffrey A Law
1999-01-29 6:41 ` Gerald Pfeifer
1999-01-29 6:48 ` Gerald Pfeifer
1999-01-31 23:58 ` Alexandre Oliva
1999-01-31 23:58 ` Andreas Jaeger
1999-01-31 23:58 ` Jeffrey A Law
1998-06-30 0:42 x86 double alignment (was egcs-1.1 release schedule) Jeffrey A Law
1998-06-30 8:19 ` gcc2 merge H.J. Lu
1998-06-30 19:49 ` Jeffrey A Law
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=36AF7591.9DE84056@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=egcs@cygnus.com \
--cc=mrs@wrs.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).