Thanks, Greg and George. I now have xlf working, and I guess my
gfortran build may be flakey, but I can live with that for now.
David
OMPI uses the fortran compiler to link a C program in order to test
the size of LOGICAL, etc. To get it to work with xlf, I had to add -
lSystemStubs to the gcc_libs entry for f77 in /etc/opt/ibmcmp/xlf/8.1/
xlf.cfg.
Greg
On Aug 30, 2005, at 11:58 AM, David Daniel wrote:
Hi Folks,
Anyone
I do. I'm compiling f77 and f90 on my MAC. Bu in order to do it I had
to install my own gfortran. Basically I use the gcc provided by
apple, and a gfortran version 4.0. Everything seems to work fine. I
get all the Fortran types with the correct size and alignment.
george.
On Aug 30, 2005
Hi,
I am using autogen.subdirs files to make autogen.sh parse my subdirs. In
each subdirs I have a configure.params file describing the Makefile to
be build (as usual).
The problem is that instead of adding the component to the variable in
the toplevel configure, it creates a separate mca_no
Hi Folks,
Anyone had any luck building fortran on Tiger, particularly f90?
I'm probably just dumb, but appended are 4 problems I've seen.
Thanks, David
1. gfortran
configure --enable-f77 --enable-f90
[snip]
*** Fortran 77 compiler
checking for gfortran... gfortran
checking whether we are
Hi all -
for those having issues with WRAPPER_EXTRA_LIBS/LDFLAGS constants
showing up in the output of mpicc, a quick workaround is to disable
the GM PTL during configure. This can be accomplished by adding the
configure flag:
--enable-mca-no-build=ptl-gm
to your configure line, then
* Jeff Squyres wrote on Tue, Aug 30, 2005 at 12:45:32PM CEST:
> Huh. And I always thought it was the other way around (you *had* to
> put "" around it or they would be treated as separate words).
They do it usually. They don't do it on the right hand side of an
assignment (i.e., after "="), nor
Huh. And I always thought it was the other way around (you *had* to
put "" around it or they would be treated as separate words).
Committed; thanks.
On Aug 29, 2005, at 12:30 PM, Ralf Wildenhues wrote:
A small patch: On one hand, Bourne shells do not do word splitting
after
parameter expans
