On Fri, Mar 17, 2006 at 12:49:16AM +0100, Steven Bosscher wrote:
> On 3/17/06, Steve Kargl <[EMAIL PROTECTED]> wrote:
>
> > If
> > you really want to expose getarg_ and iargc_, look at abort_.
>
> I really do want to somehow make it easy for people to link again
ally want to expose getarg_ and iargc_, look at abort_.
I really do want to somehow make it easy for people to link against
libgfortran when they are compiling stuff, and not get link errors.
That does mean exposing getarg_ and iargc_, however I'd be perfectly
fine with stuffing those ex
ly compatibilty issues.
Careful. libgfortran attempts to keep its namespace clean
by appending gfortran_ to its intrinsics procedure. libg2c
has no namespace and is a fine example of a garbage dump. If
you really want to expose getarg_ and iargc_, look at abort_.
Note, I oppose this type of ch
they have a getarg.c that calls C2F(getarg), with a line in one
> of the included header files that says "#define C2F(name) name##_".
> The same thing happens with iargc, so the gerarg.o object that
> the linker sees ends up calling getarg_ and iargc_.
>
> This worked Ju
(name) name##_".
The same thing happens with iargc, so the gerarg.o object that
the linker sees ends up calling getarg_ and iargc_.
This worked Just Fine with g77, and apparently it works with g95
as well. It does not work with gfortran, because we have instead
gfortran_getarg_i4 and so on.
I&
