From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Ken Woolridge <kwwoolridge@hotmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Question regarding compiling modules
Date: Wed, 28 Feb 2024 15:02:33 -0800 [thread overview]
Message-ID: <Zd-7id6rg07QHGRC@troutmask.apl.washington.edu> (raw)
In-Reply-To: <SN7PR11MB667815D31EF5D45F04BDF483B5582@SN7PR11MB6678.namprd11.prod.outlook.com>
On Wed, Feb 28, 2024 at 10:42:36PM +0000, Ken Woolridge wrote:
> A little background: I have Intel's Fortran90 compiler which
> I used for years. However, I recently had to reinstall it
> and found that the key was no longer valid. Intel did not
> have the decency to return my emails so I looked for another
> Fortran90 compiler.
Intel's OneApi is available for download and use without
a license key. This isn't the forum to discuss how to
go about getting a useable OneApi.
> I am in the process of testing gfortran. However, when I
> compile a module called MOD_WIN_APIS containing interfaces
> to Microsoft API functions I get the error:
>
> Error: Derived type '{whatever}' at (1) is being used before it is defined
>
> I have defined these types in another module named MOD_TYPES
> which is compiled prior to MOD_WIN_APIS. MOD_WIN_APIS uses MOD_TYPES
> (with the statement "USE MOD_TYPES") prior to any interfaces being defined.
>
> Why am I getting this error when the types are defined???
Stab in the dark. mod_types.mod is another directory. Try
adding the "-I. -I${path_to_mod_types.mod}" to your command line.
--
Steve
prev parent reply other threads:[~2024-02-28 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 22:42 Ken Woolridge
2024-02-28 23:02 ` Steve Kargl [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=Zd-7id6rg07QHGRC@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=kwwoolridge@hotmail.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).