From: Mumit Khan <khan@xraylith.wisc.edu>
To: Richard Stanton <stanton@haas.berkeley.edu>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: CFORTRAN for cygwin/egcs?
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.990315162021.2930I-100000@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990331194500.3AWGYcuWpVaiYy79mXolLnf8HkEbvYyVzCoamjfTeVE@z> (raw)
In-Reply-To: <000f01be6f12$cf737f60$893a85d1@CONNOR.berkeley.edu>
On Mon, 15 Mar 1999, Richard Stanton wrote:
> There's a rather useful package called CFORTRAN, that makes calling FORTRAN
> subroutines from C, and vice versa, very simple, on the machines it knows
> about.
>
> Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
> appreciate any pointers or examples you may have.
Hmmm ... it's been years since I've used, but from what I remember, it
should be pretty trivial to use with gcc/g77 on Windows32. I believe the
magic was to define -Df2cFortran (or something like that) and the rest
just worked.
One potential gotcha, and only applicable if you're using gcc/c++ as the
link driver instead of using g77, is that f77 runtime library bundled with
g77 has been renamed from libf2c.a to libg2c.a, and so you'll need to link
with -lg2c instead of -lf2c.
$ gcc -Df2cFortran -c cfile.c
$ g77 -c ffile.f
$ gcc -o mixedprog ffile.o cfile.o -lg2c
What problems have you had?
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-03-31 19:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 12:12 linking and iostreams Greg Miller
[not found] ` < 36E9744E.790549C@classic-games.com >
1999-03-12 14:34 ` Mumit Khan
1999-03-12 14:54 ` Greg Miller
[not found] ` < 36E99A6A.FC36E7F@classic-games.com >
1999-03-12 16:38 ` Mumit Khan
1999-03-12 19:14 ` Greg Miller
1999-03-31 19:45 ` Greg Miller
[not found] ` < 199903130037.SAA00256@modi.xraylith.wisc.edu >
1999-03-15 10:35 ` CFORTRAN for cygwin/egcs? Richard Stanton
[not found] ` < 000f01be6f12$cf737f60$893a85d1@CONNOR.berkeley.edu >
1999-03-15 14:27 ` Mumit Khan [this message]
[not found] ` < Pine.SUN.3.93.990315162021.2930I-100000@modi.xraylith.wisc.edu >
1999-03-15 17:58 ` Richard Stanton
[not found] ` < 000b01be6f50$74ce5a60$9e3a85d1@CONNOR.berkeley.edu >
1999-03-16 0:47 ` Mumit Khan
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` Richard Stanton
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` Richard Stanton
1999-03-31 19:45 ` linking and iostreams Mumit Khan
1999-03-31 19:45 ` Greg Miller
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` Greg Miller
1999-03-16 3:02 CFORTRAN for cygwin/egcs? Billinghurst, David (RTD)
1999-03-31 19:45 ` Billinghurst, David (RTD)
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=Pine.SUN.3.93.990315162021.2930I-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=stanton@haas.berkeley.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).