From: Hans Lonsdale <hanslonsdale@mailfence.com>
To: Tom Kacvinsky <tkacvins@gmail.com>, Gcc Help <gcc-help@gcc.gnu.org>
Subject: Re: no input files when calling gfortran
Date: Sun, 1 Jan 2023 17:05:01 +0100 (CET) [thread overview]
Message-ID: <1655625240.766289.1672589101799@ichabod.co-bxl> (raw)
In-Reply-To: <CAG_eJLfQ6cTV3ocyLs87nyTQPYDbRaSFX7ide2SHJqpPO0UhHQ@mail.gmail.com>
> ----------------------------------------
> From: Tom Kacvinsky via Gcc-help <gcc-help@gcc.gnu.org>
> Sent: Sun Jan 01 16:48:06 CET 2023
> To: Gcc Help <gcc-help@gcc.gnu.org>
> Subject: Re: no input files when calling gfortran
>
>
> On Sun, Jan 1, 2023 at 10:34 AM Hans Lonsdale via Gcc-help <
> gcc-help@gcc.gnu.org> wrote:
>
> >
> >
> > January 1, 2023 at 2:31:28 PM CET Jonathan Wakely <jwakely.gcc@gmail.com>
> > wrote:
> >
> > On Sun, 1 Jan 2023, 11:43 Hans Lonsdale via Gcc-help, <
> > gcc-help@gcc.gnu.org> wrote:
> >
> > Am trying to compile a free-format fortran file with some subroutines in
> > it, with gfortran complaining
> > about the file. What is going on?
> >
> > gfortran -O3 -ffree-form -o kamkrai-sort.f
> > gfortran: fatal error: no input files; unwilling to write output files
> > compilation terminated.
> >
> > The -o option names the output file, but you have told the compiler to use
> > your input file as the output file.
> >
> > What is the appropriate command that generates the object file only ?
> >
>
> gfortran -O3 -ffree-form -c kamkrai-sort.f
I tried your suggestion but I am getting
recursive subroutine quicksort (array)
Error: Unclassifiable statement at (1)
end subroutine quicksort
Error: Expecting END PROGRAM statement at (1)
But this is just a file with some variables and a recursive subroutine.
--
Sent with https://mailfence.com
Secure and private email
prev parent reply other threads:[~2023-01-02 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 0:45 Hans Lonsdale
2023-01-01 13:31 ` Jonathan Wakely
2023-01-01 15:14 ` Hans Lonsdale
2023-01-01 15:48 ` Tom Kacvinsky
2023-01-01 16:05 ` Hans Lonsdale [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=1655625240.766289.1672589101799@ichabod.co-bxl \
--to=hanslonsdale@mailfence.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tkacvins@gmail.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).