On Tue, Jun 17, 2003 at 08:51:29AM -0400, Jeff Squyres wrote:
> On Tue, 17 Jun 2003, [ISO-8859-1] Richard Büssow wrote:
>
> > -----
> > ./configure --prefix=/opt/lam-6.5.9 --with-cc=icc --with-cflags="-O3
> > -tpp7 -xW -Xa -w -ipo -ipo_obj" --with-cxx=icc --with-cxx flags="-O3
> > -tpp7 -xW -Xa -w -ipo -ipo_obj" --with-fc=ifc --with-fflags="-O3 -tpp7
> > -xW -w -ipo -ipo_opj" --with-trillium --with-rpi=tcp --with-rsh=rsh
> > -----
> > I get some output, and then:
> > [snipped]
>
> What is happening here is that LAM is trying to determine which symbol
> convention is being used by the fortran compiler. It compiles a simple
> fortran file and looks at the resulting symbols.
>
> The error is occuring because the compiler is generating object files in a
> non-standard filename. This appears to be because of the -ipo switch --
> ifc is generating the output in a .il file instead of a .o file. Hence,
> LAM's configure is looking at the .o file and seeing dummy output (and
> therefore getting confused). Additionally, even if configure did know to
> look at the .il file, nm doesn't know how to parse it (it appears to be an
> intel-specific format).
you can use the -ipo_obj to build the usual .o file :)
just my 2 cents
Tru
--
Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/
mailto:tru_at_[hidden] | tel/fax +33 1 45 68 87 37/19
Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France
|
