From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: fheitka@ibm.net
Cc: egcs@cygnus.com
Subject: Re: compiling libstdc++/libg++ 2.8.1.1 with egcs-1.1.1?
Date: Wed, 30 Dec 1998 11:22:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.9812302021400.24619-100000@markab.dbai.tuwien.ac.at> (raw)
In-Reply-To: <199812270141.BAA58046@out2.ibm.net>
On Sat, 26 Dec 1998, Frederick V. Heitkamp wrote:
> Can I compile libstdc++/libg++ 2.8.1.1 with egcs-1.1.1?
Have you checked the FAQ at http://egcs.cygnus.com/faq.html ?
It has an entry regarding libg++.
Gerald
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1998-12-30 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-26 17:42 Frederick V. Heitkamp
1998-12-28 2:08 ` Andreas Schwab
1998-12-30 11:22 ` Gerald Pfeifer [this message]
[not found] <199812292203.OAA24955@kankakee.wrs.com>
1998-12-30 3:46 ` fheitka
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=Pine.GSO.4.05.9812302021400.24619-100000@markab.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=egcs@cygnus.com \
--cc=fheitka@ibm.net \
/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).