Re: [AMBER-Developers] intel64: feupdateenv is not implemented and will always fail

From: Lachele Foley <lfoley.ccrc.uga.edu>
Date: Wed, 17 Feb 2010 15:23:34 -0500

I tried Googling:

http://software.intel.com/en-us/forums/showthread.php?t=62806

""""
Re: Warning about feupdateenv is not implemented
I had this problem in the past. The problem is the you are linking against the Intel math library only. The Intel math library (libimf) has optimized replacements for many of the routines in the system math library (libm). However, the Intel math library does not provide replacements for all functions.

The solution is simple. Always link against both math libraries: libimf libm
""""


:-) Lachele 
--
B. Lachele Foley, PhD '92,'02
Assistant Research Scientist
Complex Carbohydrate Research Center, UGA
706-542-0263
lfoley.ccrc.uga.edu
----- Original Message -----
From: Jason Swails
[mailto:jason.swails.gmail.com]
To: AMBER Developers Mailing List
[mailto:amber-developers.ambermd.org]
Sent: Wed, 17 Feb 2010 15:15:11
-0500
Subject: Re: [AMBER-Developers] intel64: feupdateenv is not
implemented and 	will always fail
> Hello,
> 
> On Wed, Feb 17, 2010 at 3:04 PM, Lachele Foley <lfoley.ccrc.uga.edu> wrote:
> > During the install of AmberTools (from CVS last night), I got complaints
> that claim to be warnings, but include the word "fail".  Then I got the
> same complaints during the testing phase, despite declarations of passing.
>  Is ok?  Not ok?
> >
> > System info (more upon request):
> >
> > Linux yeats 2.6.9-67.0.4.EL_SFS2.3_0smp #1 SMP Thu Nov 27 12:58:33 GMT
> 2008 x86_64 x86_64 x86_64 GNU/Linux
> > icc (ICC) 11.0 20090318
> > ifort (IFORT) 11.0 20090318
> >
> >
> > Complaint info (more upon request):
> >
> > ================= during compile ============================
> > tss_main.c(300): warning #167: argument of type "POINT_T *" is
> incompatible with parameter of type "REAL_T={double} *"
> >  setmol_from_xyz(  &mcomp, STEMP( __st0002__, SPRINTF( assert( (
> snprintf( NAB_rsbuf, 10000, "%d::", m ) ) < 10000 ), NAB_strcpy(
>  &__st0001__, NAB_rsbuf ) ) ), pts );
> >                                                  
>                                                  
>                                                  
>            ^
> >
> > /programs/amber11_20100216/bin/nab -o tss_main tss_main.o
> > tss_main.o(.text+0x7b0): In function `main':
> > : warning: the use of `tmpnam' is dangerous, better use `mkstemp'
> > /opt/intel/Compiler/11.0/083/lib/intel64/libimf.so: warning: warning:
> feupdateenv is not implemented and will always fail
> > /programs/amber11_20100216/bin/nab -c tss_next.nab
> > /programs/amber11_20100216/bin/nab -o tss_next tss_next.o
> > /opt/intel/Compiler/11.0/083/lib/intel64/libimf.so: warning: warning:
> feupdateenv is not implemented and will always fail
> > mv matextract matgen matmerge matmul \
> >        transform tss_init tss_main \
> >        tss_next /programs/amber11_20100216/bin
> > make[1]: Leaving directory `/programs/amber11_20100216/src/nss'
> >
> > Installation of AmberTools, version 1.3 is complete at Wed Feb 17 16:27:35
> GMT 2010.
> > ================= end during compile ============================
> > =================================================================
> >
> >
> > ================= sample complaints during tests
> ============================
> > =====================================================
> > Running Reflexive test:
> >
> > /opt/intel/Compiler/11.0/083/lib/intel64/libimf.so: warning: warning:
> feupdateenv is not implemented and will always fail
> >        PASSED
> > =====================================================
> > Running test of hashed arrays:
> >
> > /opt/intel/Compiler/11.0/083/lib/intel64/libimf.so: warning: warning:
> feupdateenv is not implemented and will always fail
> >        PASSED
> > =====================================================
> > Running test to compute chemical shifts
> >   (This tests many parts of the compiler and libraries)
> >
> > /opt/intel/Compiler/11.0/083/lib/intel64/libimf.so: warning: warning:
> feupdateenv is not implemented and will always fail
> >        PASSED
> > =====================================================
> > Running test to do simple minimization
> >   (This tests the molecular mechanics interface)
> >
> > /opt/intel/Compiler/11.0/083/lib/intel64/libimf.so: warning: warning:
> feupdateenv is not implemented and will always fail
> >        PASSED
> > =====================================================
> 
> I have never not gotten that warning using the intel compilers,
> regardless of what I'm building.  Friends have gotten it, too,
> building ab-initio codes as well.  I don't think we're using
> feupdateenv anywhere, so it shouldn't be a problem?  It's definitely
> an intel compiler thing, not an amber thing.
> 
> In any case, it hasn't been a problem to date.  Perhaps others are
> more knowledgeable about what this non-implemented, always-failing
> function is and why intel insists on having such a function in one of
> their libraries.
> 
> All the best,
> Jason
> 
> -- 
> ---------------------------------------
> Jason M. Swails
> Quantum Theory Project,
> University of Florida
> Ph.D. Graduate Student
> 352-392-4032
> 
> _______________________________________________
> 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 Wed Feb 17 2010 - 12:30:05 PST
Custom Search