Re: [AMBER-Developers] finding intel libraries

From: Volodymyr Babin <vbabin.ncsu.edu>
Date: Thu, 18 Mar 2010 22:15:57 -0400 (EDT)

I am not sure I understand correctly, but maybe you meant
something like

IFORT_BIN=`which ifort`
IFORT_HOME=`dirname $IFORT_BIN`
IFORT_LIBDIR=`echo $IFORT_HOME | sed -e 's!/bin$!/lib!'`

then flibs_arch would be -L$IFORT_LIBDIR -l...

another way is to parse the output of 'ifort -dryrun nothing.f'
[looks cumbersome]

best,

Volodymyr

On Thu, March 18, 2010 19:56, case wrote:
> We now have the following in configure, for intel compilers:
>
> flibs_arch=`echo $LD_LIBRARY_PATH | sed -e 's/^\(.\)/ -L\1/' -e
's/:/
> -L/g'`
> flibs_arch=`echo $flibs_arch | sed -e 's/-L[ ]//g' -e 's/-L$//g'`
>
> First, there is no reason to suppose that there won't be lots of bad
LD_LIBRARY_PATH environment variables out there.
>
> Second, this can make FLIBS impossibly long, even for me: by FLIBS variable
> is about 6 lines long, and it take nab forever to link.
>
> Does anyone have a thought of a better way? Is there institutional
memory
> of what this used to be, and if we can't make something simpler?
>
> ...thx...dac
>
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
>




_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Mar 18 2010 - 19:30:04 PDT
Custom Search