<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Best to use: composerxe-2011.3.174<br>
<br>
Search the mailing list and reference:<br>
<br>
<a class="moz-txt-link-freetext" href="http://zeus.theochem.tuwien.ac.at/pipermail/wien/2012-January/016045.html">http://zeus.theochem.tuwien.ac.at/pipermail/wien/2012-January/016045.html</a><br>
<br>
Of note only, update 11 of composer xe was recently released.
However, Wien2k users could have issues with it as the bug fixes
seem minor since update 9 and 10 (having errors on some systems).
Though, update 11 seems to work fine on my Debian squeeze system
with AMD processor.<br>
<br>
/lib/libc.so.6<br>
<br>
returns version 2.11.3 for glibc<br>
<br>
I don't see many reports in the Linux community, but it seems to
me that recent glibc (such as unpatched versions 2.12 and 2.14)
might be buggy.<br>
<br>
The RedHat 6 documentation states the following, which could
explain why the errors seem to be occurring with Intel iprocessors
with AVX:<br>
<br>
<i>BZ#752122<br>
Previously, glibc's dynamic loader incorrectly detected Advanced
Vector Extensions (AVX) capabilities and could terminate
unexpectedtly with a segmentation fault. This update fixes the
AVX detection and the problem no longer occurs. </i><br>
<br>
<a class="moz-txt-link-freetext" href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.3_Technical_Notes/glibc.html#RHBA-2012-0763">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.3_Technical_Notes/glibc.html#RHBA-2012-0763</a><br>
<br>
It looks like patched versions were recently released (on
06-20-2012) to address these issues.<br>
<br>
CentOS 6:
<a class="moz-txt-link-freetext" href="http://www.latestonlinux.com/2012/05/centos-announce-ceba-20120566-centos-6-glibc-update/">http://www.latestonlinux.com/2012/05/centos-announce-ceba-20120566-centos-6-glibc-update/</a><br>
RedHat 6: <a class="moz-txt-link-freetext" href="https://rhn.redhat.com/errata/RHBA-2012-0763.html">https://rhn.redhat.com/errata/RHBA-2012-0763.html</a><br>
<br>
Currently, there is 96 new bug reports for glibc and a new
2.16-tps version seems to be available for certain versions of
Ubuntu according to:<br>
<br>
<a class="moz-txt-link-freetext" href="https://launchpad.net/ubuntu/+source/glibc">https://launchpad.net/ubuntu/+source/glibc</a><br>
<br>
However, Wien2k user reports confirming resolution of the memory
errors after updating/patching the glibc library would be needed.
The other problem is that it is dangerous to update glibc as it
can break the operating system:<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.centos.org/modules/newbb/viewtopic.php?topic_id=20361">http://www.centos.org/modules/newbb/viewtopic.php?topic_id=20361</a><br>
<br>
I suppose that reinstalling a newer version of the operating
system if its available might be the easier and safer way to go,
unless some here can share their experience on how to safely
update glibc.<br>
<br>
On 6/29/2012 7:41 AM, Antonio Vanderlei dos Santos - Fisica wrote:<br>
</div>
<blockquote
cite="mid:48d4ce2984017713342ab8988645611a@santoangelo.uri.br"
type="cite">Dear Users
<div>
<p>Which Fortran compiler for Wien2K has the following
configuration:</p>
<p>Description: Ubuntu 10.04.3 LTS</p>
<p>Release: 10.04</p>
<p>Codename: lucid</p>
<p>help me ?</p>
<br>
</div>
</blockquote>
</body>
</html>