[GRASS5] Re: BLAS et al

[John Huddleston]

Hi David,

I have Blas compiled and it is available under the Cygwin environment
for Windows NT and 2000 as well as Solaris.  DITTO with LAPACK.

Will my knowledge of Grass and its use in this application, I would
say right off that the best way to use Blas library is to incorporate
it in the src/CMD/head/os_specific/xxx files where xxx refers to 
your specific platform.  When you make a new or edit an old
Gmakefile, add the $(BLASLIB) to the library line.   Ditto with
LAPACK.

You compile it locally on your machine.  Put it into your
/usr/local/lib area and if necessary run a ranlib on it.

Give me some specific section in grass and I will help 
you if you need some assistance.

John Huddleston

----- Original Message ----- 
From: "David D Gray" <ddgray at armadce.demon.co.uk>
To: "John Huddleston" <jhudd at lamar.colostate.edu>
Sent: Wednesday, September 20, 2000 11:53 AM
Subject: BLAS et al


> 
> John
> 
> Perhaps as you know something about the linear algebra routines, you
> could advise me on one thing: Are there any special provisions that you
> know of that might need to be taken care of in installing BLAS and
> LAPACK into GRASS? I mean for things like cross-platform portability. I
> am trying to decide whether we
> 
> 1) Link to system libs, thus making these a dependency of GRASS.
> 
> or  
> 
> 2) Bundle BLAS and LAPACK with GRASS. Then there may be platform issues
> in compilation.
> 
> On linux/unix/i386, we just need a link to g2c.h (or f2c.h) and a
> prototype file, can be done with `f2c -P'. Markus has suggested a set of
> wrapper routines, functions and macros, for making the special features
> (re fortran) transparent to developers.
> 
> Option 1 would enable easier plugin to local optimised libraries,
> whether created by hand (assembler routines etc. by the system vendor)
> or something like ATLAS, but might be prone to version skew for others.
> 
> 
> On another point, in your reply to Rich Shephard's posting on the
> development model, you said:
> 
> 
> John Huddleston wrote:
> > 
> > [...]
> > Third, and a curious turn of events, ESRI's next release will
> > no longer support Avenue scripts and ***will not support shapefiles***.
> > All the developers who have put time and money into developing
> > in these two areas will not have an upgrade path.
> 
> 
> [my emphases] 
> 
> Can you explain more precisely? I knew Avenue was getting dropped (and
> Python maybe adopted), but I thought that shapefiles was just up for an
> upgrade?
> 
> Thanks, regards
> 
> David


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'