From: Zane Dodson <zdodson@zdodson.com>
To: help-gcc@prep.ai.mit.edu
Cc: Agw47@aol.com
Subject: Re: compiler errors
Date: Mon, 29 Apr 2002 16:57:00 -0000 [thread overview]
Message-ID: <20020429155120.A23482@xi.zdodson.com> (raw)
In-Reply-To: <1a1.176e25b.29ff01c3@aol.com>; from Agw47@aol.com on Mon, Apr 29, 2002 at 04:06:27PM -0400
On Mon, Apr 29, 2002 at 04:06:27PM -0400, Agw47@aol.com wrote:
| including all the includes? how can i produce a listing so i can find the
| errors?
Try the `-save-temps' flag. See gcc(1) (excerpt below).
-save-temps
Store the usual "temporary" intermediate files per
manently; place them in the current directory and
name them based on the source file. Thus, compil
ing `foo.c' with `-c -save-temps' would produce
files `foo.cpp' and `foo.s', as well as `foo.o'.
Best regards,
--
Zane Dodson
zdodson@zdodson.com
next prev parent reply other threads:[~2002-04-29 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 13:12 Agw47
2002-04-29 13:25 ` John Love-Jensen
2002-04-29 16:57 ` Zane Dodson [this message]
[not found] <105.14f5db73.2a002122@aol.com>
2002-04-30 11:49 ` Zane Dodson
[not found] <616BE6A276E3714788D2AC35C40CD18D39468A@whale.softwire.co.uk>
2002-02-01 1:28 ` Compiler errors Rupert Wood
-- strict thread matches above, loose matches on Subject: below --
2002-02-01 1:22 Dimitri Frederickx
2002-02-01 14:03 ` Alexandre Oliva
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=20020429155120.A23482@xi.zdodson.com \
--to=zdodson@zdodson.com \
--cc=Agw47@aol.com \
--cc=help-gcc@prep.ai.mit.edu \
/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).