From: "David W. Banks" <dbanks@cislunar.com>
To: egcs@cygnus.com, Kate Hedstrom <kate@ahab.rutgers.edu>
Subject: Re: g77 and cpp. Single quote in comment line.
Date: Sat, 19 Sep 1998 17:40:00 -0000 [thread overview]
Message-ID: <3603EECD.14870F51@cislunar.com> (raw)
In-Reply-To: <199809191312.JAA20531@ahab.rutgers.edu>
Kate Hedstrom wrote:
>
> Meanwhile, "cpp -traditional" should do the job. This is how cpp gets
> called if you ask g77 to do it for you (g77 foo.F).
>
Maybe this could be mentioned in the man page for cpp? When cpp failed
that's where I went to look for a solution, Some mention of -traditional
being needed for .F files (or that g77 makes the call on it's own and that
there is no need for an explicit call) would have kept me from loading up
your mail server with this RTFM type of question.
Thanks for all the help,
-Dave
next prev parent reply other threads:[~1998-09-19 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-19 6:06 Kate Hedstrom
1998-09-19 17:40 ` David W. Banks [this message]
1998-09-19 18:47 ` Richard Henderson
1998-09-21 10:17 ` Craig Burley
1998-09-22 2:50 ` Dave Love
-- strict thread matches above, loose matches on Subject: below --
1998-09-17 11:14 David W. Banks
1998-09-18 2:21 ` Dave Love
1998-09-19 1:36 ` Craig Burley
1998-09-19 12:03 ` Dave Love
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=3603EECD.14870F51@cislunar.com \
--to=dbanks@cislunar.com \
--cc=egcs@cygnus.com \
--cc=kate@ahab.rutgers.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).