From @gk @end|ng |rom troutm@@k@@p|@w@@h|ngton@edu  Sat May  4 18:43:57 2019
From: @gk @end|ng |rom troutm@@k@@p|@w@@h|ngton@edu (Steve Kargl)
Date: Sat, 4 May 2019 09:43:57 -0700
Subject: [Rd] R problems with lapack with gfortran
In-Reply-To: <D521C66E-D67E-4C17-98EF-D651026561ED@gmail.com>
References: <ff60d7f9-e54d-473a-bc85-7989abc887da@tkoenig.net>
 <b24b0ef5-1f45-1a03-4153-f335e4f1f8a5@gmail.com>
 <2e68f333-1d10-02d4-3560-4b1b9d773a52@tkoenig.net>
 <6E812A6F-91B2-4412-A536-2CD672C5F4BA@xs4all.nl>
 <D521C66E-D67E-4C17-98EF-D651026561ED@gmail.com>
Message-ID: <20190504164357.GA15478@troutmask.apl.washington.edu>

On Sat, May 04, 2019 at 06:05:48PM +0200, peter dalgaard wrote:
> 
> - figure out Fortran2003 specification for C/Fortran interoperability
> -- this _sounds_ like the right solution, but I don't think many
> understand how to use it and what is implied (in particular, will it
> require making changes to LAPACK itself?)

This is probably the best solution as it should allow portability
to any Fortran processor that supports F2003 or newer standard.
See the gtk-fortran project.  It has a python program that was
used to generate the needed ISO C interfaces.

-- 
Steve



[Rd] R problems with lapack with gfortran
Steve Kargl