From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: klaxi@t-online.de
Cc: gcc@gcc.gnu.org
Subject: Re: Problems trying to compile g++ under NT
Date: Tue, 28 Mar 2000 14:55:00 -0000 [thread overview]
Message-ID: <200003282248.AAA01240@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <001301bf98e6$84b64120$0300a8c0@Home.de>
> I'm trying to compile g++ 2.95.2 under Windows NT with VisualC++
> 8.0. Documentation says its possible, but I got lots of problems.
Where did you read its possible? Compiling the C compiler might be
supported; compiling the C++ compiler is not - that is supposed to be
build with the C compiler generated in stage 1.
> Is there a chance to avoid those PVPROTO,VPROTO an PROTO-stuff?
What do you mean, avoid? You can certainly replace them using global
search-and-replace in your editor, provided you end up with ANSI C
signatures afterwards, and provided your bootstrap compiler supports
ANSI C. It would be better if you get them defined, though.
Alternatively, you could start with a gcc 2.96 snapshot, where these
are replaced with the PARAMS macros.
> Is there any further information available about how to compile under NT,
> especially what steps does it take, what compiler-options to use, which
> files are really needed, compiling with g++-include-dir or the
> M$-include-dir ...
Please have a look at
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
Regards,
Martin
prev parent reply other threads:[~2000-03-28 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-17 18:44 C++ front-end / C++ compiler Christian Baxmann
2000-02-18 0:27 ` Martin v. Loewis
2000-03-28 10:51 ` Problems trying to compile g++ under NT Christian Baxmann
2000-03-28 14:55 ` Martin v. Loewis [this message]
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=200003282248.AAA01240@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=klaxi@t-online.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).