I have lost the thread where I alluded to a bug in the intel compilers
before version 10.1.021. A subtle bug that comes out with certain
systems under certain conditions. I have just repeated the gentoo's
people observations. In the past, version 10.1.015 worked well for me,
while a slight change prevented compiling.
Thus, it was the compiler, not the latest OS or hardware that
prevented me compiling amber9 with ifort. Now, overcome the compiler
issue, amber9 compiled plainly with ifort, like amber10, on the latest
debian amd64 lenny and contemporary multiCPU hardware..
thanks a lot for all the time you have spent helping me
francesco
On Thu, Apr 9, 2009 at 1:39 AM, Atro Tossavainen
<atro.tossavainen+amber.helsinki.fi> wrote:
>> Yes, I had also seen that and have made deb packages of the 10.1.022
>> version
>
> Make sure your shell startup scripts point all paths at the current
> version. If you ran against old libraries that were buggy you would
> most likely continue to experience the effects of old bugs.
>
> (The use of -rpath during linking is highly recommended as opposed to
> setting LD_LIBRARY_PATH at run time, not the least because it hardcodes
> the paths to the "right" library files in the executables themselves.)
>
> --
> Atro Tossavainen (Mr.) / The Institute of Biotechnology at
> Systems Analyst, Techno-Amish & / the University of Helsinki, Finland,
> +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own.
> < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS
>
> _______________________________________________
> AMBER mailing list
> AMBER.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber
>
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Wed May 20 2009 - 11:44:30 PDT
