Dear list,
if I call
./configure --enable-shared F77=mpif77 ...
where mpif77 translates to
ifort -I/opt/parastation/mpi2-intel/include
-L/opt/parastation/mpi2-intel/lib -Wl,-rpath
-Wl,/opt/parastation/mpi2-intel/lib -lmpich -lpthread
-L/opt/parastation/lib64 -Wl,-rpath,/opt/parastation/lib64
-W
Hello Christian,
* Christian Rössel wrote on Fri, Dec 10, 2010 at 02:56:51PM CET:
> ./configure --enable-shared F77=mpif77 ...
>
> where mpif77 translates to
>
> ifort -I/opt/parastation/mpi2-intel/include
> -L/opt/parastation/mpi2-intel/lib -Wl,-rpath
> -Wl,/opt/parastation/mpi2-intel/lib -lmpi
On Thu, Oct/21/2010 06:13:03AM, Ralf Wildenhues wrote:
> Hello Ethan,
>
> * Ethan Mallove wrote on Wed, Oct 20, 2010 at 10:32:11PM CEST:
> > > It looks like that gives us the link line we want, yet we still get the
> > > libimf.so dependency:
> > >
> > > $ /bin/sh ../../../libtool --tag=CC --mo
* Ethan Mallove wrote on Fri, Dec 10, 2010 at 07:41:20PM CET:
> On Thu, Oct/21/2010 06:13:03AM, Ralf Wildenhues wrote:
> > Pass -Wc,-static-intel instead.
>
> This works like a charm for shared libraries, but for standalone
> executables I get an error like this:
>
> ...
> icc: command line w