From: Frank Packenham <Etc@Weirdness.com>
To: gnu-win32@cygnus.com
Subject: RE: gcc problem
Date: Thu, 23 Oct 1997 07:26:00 -0000 [thread overview]
Message-ID: <199710231418.XAA02817@ares.levels.unisa.edu.au> (raw)
Thanks everyone. The problem was indeed borland cpp.exe, removing borland from the path helped solve the problem. I have two other questions: is lex available for win32 ? is imake or equivalent available for win32? Please e-mail to my address as the volume of the list was too much for me to handle, so I only monitor the archives now. TIA -------------------------------- Frank Packenham CIS (Hons) e-mail: cisfjp @ cis. unisa.edu.au Why not vistit my Website: http://www.cis.unisa.edu.au/~9202917w/ DECS Electronic Media Services
next reply other threads:[~1997-10-23 7:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-23 7:26 Frank Packenham [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 12:49 Lauer Rainer
2004-03-02 12:53 ` Laurent Vaucher
2004-03-02 14:56 ` Gerrit P. Haase
2004-03-02 15:57 ` Gareth Pearce
2003-09-14 21:00 swa004
2002-03-21 5:39 GCC problem Robert Collins
2002-03-21 5:17 Mike Hayden
2002-03-21 5:26 ` David Starks-Browning
[not found] <Pine.LNX.4.33.0112142057150.7431-100000@heros.knurow.tpsa. pl>
2001-12-14 11:41 ` Larry Hall (RFK Partners, Inc)
2001-12-14 11:11 gahan
2001-09-06 7:31 gcc problem Peter Buckley
2001-09-06 7:36 ` Larry Hall (RFK Partners, Inc)
2001-09-06 6:45 Peter Buckley
2001-09-06 7:17 ` Dominik Zalewski
2001-09-06 6:41 Dominik Zalewski
2001-07-27 10:14 gcc_Problem Mr.Serkan Gumusbicak
2001-07-27 11:50 ` gcc_Problem Carl Hetherington
2000-08-11 16:12 gcc problem Consequator
2000-08-11 17:22 ` Chris Faylor
2000-08-12 3:37 ` Consequator
1997-10-20 19:25 Colin Peters
1997-10-21 7:44 ` Steven J. Zeil
1997-10-20 3:21 Frank Packenham
1997-10-20 6:00 ` Fergus Henderson
1997-03-10 4:11 Jon Thackray
1997-03-10 6:04 ` Jim Balter
1997-03-10 6:11 ` Jon Thackray
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=199710231418.XAA02817@ares.levels.unisa.edu.au \
--to=etc@weirdness.com \
--cc=gnu-win32@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).