Why not edit libtool to see what it is doing (it's just a script)
- you will get a lot of output:
Add a "set -x" as the second line and stand well back :-)
#! /bin/sh
set -x
Mostyn
On Wed, 20 Jun 2007, Andrew Friedley wrote:
I'm not seeing anything particularly relevant in the libtool
docume
On Jun 20, 2007, at 11:41 AM, Andrew Friedley wrote:
I'm not seeing anything particularly relevant in the libtool
documentation. I think this might be referring to hardcoding paths in
shared libraries?
Using pathf90 for both FC and F77 does not change anything. Should
have
been more clear
I'm not seeing anything particularly relevant in the libtool
documentation. I think this might be referring to hardcoding paths in
shared libraries?
Using pathf90 for both FC and F77 does not change anything. Should have
been more clear in my first email -- gcc 3.4.5 using pathf90 for FC
wo
It could be; I didn't mention it because this is building ompi_info,
a C++ application that should have no fortran issues with it.
But then again, who knows? Maybe you're right :-) -- perhaps libtool
is just getting confused because you used g77 and pathf90 -- why not
use pathf90 for both
Isn't this another case of trying to use two different Fortran compilers
at the same time?
On Tue, 2007-06-19 at 20:04 -0400, Jeff Squyres wrote:
> I have not seen this before -- did you look in the libtool
> documentation? ("See the libtool documentation for more information.")
>
> On Jun 19
I have not seen this before -- did you look in the libtool
documentation? ("See the libtool documentation for more information.")
On Jun 19, 2007, at 6:46 PM, Andrew Friedley wrote:
I'm trying to build Open MPI v1.2.2 with gcc/g++/g77 3.4.4 and
pathf90 v2.4 on a linux system, and see this e
I'm trying to build Open MPI v1.2.2 with gcc/g++/g77 3.4.4 and pathf90
v2.4 on a linux system, and see this error when compiling ompi_info:
/bin/sh ../../../libtool --tag=CXX --mode=link g++ -g -O2
-finline-functions -pthread -export-dynamic -o ompi_info
components.o ompi_info.o output.o p
