From: Peter Seebach <seebs@monolith.solon.com>
To: egcs@cygnus.com
Subject: Minor SS issue...
Date: Tue, 19 Aug 1997 16:06:35 -0000 [thread overview]
Message-ID: <199708191554.KAA02170@monolith.solon.com> (raw)
Is there a point in egcs-ss-970814 extracting into
egcs-ss-970814/egcs-ss-970814
?
I feel compelled to say "I heard you the first time". :)
-s
WARNING: multiple messages have this Message-ID
From: Thomas Weise <tw4@irz301.inf.tu-dresden.de>
To: egcs@cygnus.com
Subject: gcc installation
Date: Tue, 19 Aug 1997 17:54:31 -0000 [thread overview]
Message-ID: <199708191554.KAA02170@monolith.solon.com> (raw)
Message-ID: <19970819175431.Xmv-DdPxugpJ9Bw-VxoNus_CuBXKZdIPi34oU9hI2bU@z> (raw)
Hi,
so far I've installed snapshot egcs-ss-970814 successfully, and this
is not a bug report for gcc itself. But can someone please tell me,
why (1) there will be no configuration spec installed (on Linux
/usr/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.90.00/specs) and whether
(2) g++ seems to be no longer supported (I know that it just calls gcc,
however I've installed both languages, c AND c++).
Apart from this I'm really impressed. All of the C++ bugs I've had on my
list have been fixed (and there were a few). I'm wondering why this
version shouldn't be better than the broken 2.7.2 (at least some FSF
people might belief this..)
Thomas.
Thomas Weise, http://www.inf.tu-dresden.de/~tw4
Dresden University of Technology, Department of Computer Science
next reply other threads:[~1997-08-19 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-19 16:06 Peter Seebach [this message]
1997-08-19 17:54 ` gcc installation Thomas Weise
1997-08-19 19:08 alpha-linux-gnulibc1 patch Richard Henderson
1997-08-19 19:12 ` Minor SS issue 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=199708191554.KAA02170@monolith.solon.com \
--to=seebs@monolith.solon.com \
--cc=egcs@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).