This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: *.f *.c linking problem - g77 = gcc (options)?
- To: Craig Burley <burley at gnu dot org>
- Subject: Re: *.f *.c linking problem - g77 = gcc (options)?
- From: "Dr H. T. Leung" <htl10 at cus dot cam dot ac dot uk>
- Date: Wed, 15 Jul 1998 15:40:59 +0100 (BST)
- cc: kunert at physik dot tu-dresden dot de, egcs-bugs at cygnus dot com
The original fortran/C code and in particular the Makefile was fairly
SUN-specific; the make file was very incomprehensible with a lot of string
substitutions, etc (forgodsake there are only 16 source files for 4
binaries - hardcoding the file names in the Makefile would be half the
length).
At one point I could get the code to compile by issuing the separate g77
commmands directly, with a ripped and broken libf2c.a (removing main.o)
and extra lines in the C main() wrapper about xargv/xargc, so I don't have
an immediate problem; just though it would be nice to have it working as
it was; and it is probably not right for libf2c to have a main.o just in
case somebody want to write a c wrapper for fortran routines.
Except I have two more sets of programs to port, from the same guy...
On Wed, 15 Jul 1998, Craig Burley wrote:
> My guess is that the original problem was partly due to the Fortran
> code being compiled including calls to GETARG or IARGC. It's hard
> to tell without more complete bug reports.
>
> tq vm, (burley)