On Apr 20, 2005, at 8:31 AM, eric_at_[hidden] wrote:
> I think that I'm already doing this (with pgi 5.2-4, not 6 yet..) and
> gcc.
>
> I thought that it was all about setting the environment variables
> before
> ./configure 'ing lam-mpi:
>
> export FC=pgf90
> export FFLAGS=" -fastsse -tp k8-64 -Minfo -V -g77libs "
> export CC=gcc
> export CFLAGS="-O3"
> export CPPFLAGS="-O3"
> export CXX=g++
> export CXXFLAGS="-O3"
> export F77=pgf77
>
> This seems to work fine for separate fortran and c++ mpi code, but
> perhaps my
> setup is horribly broken and I'll have to break down and buy pgcc
> after all...
If you aren't getting pages and pages of nasty, incomprehensible error
messages whenever you try to link, your setup is fine.
In general, the Linux commercial compiler people are pretty good about
keeping things working between gcc/g++ and their Fortran offering.
Sometimes life gets sticky when you try to do that on other platforms,
or when you try to use g77 and a commercial C compiler (I can't for the
life of me imagine why anyone would want to do that, but I'm never
surprised by anything any more).
So in short, I wouldn't worry too much. If you're worried, run the LAM
test suite. It does a reasonable job at finding things like compiler
combinations gone bad.
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
