From: Chi-Cheng Chiu (ccchiu_at_student.utdallas.edu)
Date: Thu Aug 07 2008 - 11:17:16 CDT
Thanks for the idea!
We compiled NAMD linking to Tcl8.5 by setting up the
TCLLIB=-L/usr/lib64 -ltcl8.5 -ldl
We also tried setup env
but we still get "signal 11" error when running NAMD through mpirun
with tclforce turn on.
In NAMD archive, there's an article saying that NAMD hasn't been tested
with Tcl8.5. Could the problem be the compatibility of Tcl 8.5 wiht
Thanks in advance
Axel Kohlmeyer wrote:
>On Wed, 6 Aug 2008, Chi-Cheng Chiu wrote:
>CCC> Hi All,
>CCC> We compile charm++(version 6.0) and namd on a cluster with AMD
>CCC> 280 and Myrinet MX connection using MPI and PGI compiler. We can
>why PGI? g++/gcc is usually significantly faster _and_ much more
>CCC> NAMD with mpirun normally. Yet if we turn on TclForce, NAMD
>CCC> with the following error info while loading the atom's coordinate:
>CCC> /net/ss/cm/u1/son051000/N/Linux-amd64-MPI/namd2:signal 11
>CCC> MX:s47.utdallas.edu:Remote endpoint is closed,
>CCC> We are not sure which part of NAMD went wrong. Does anyone have an
>CCC> about this?
>most likely the tcl interpreter? without seeing what was leading up
>to the segfault (=signal 11) it is difficult to tell.
>please also see the discussion on the very same subject of compiling
>and running with tcl from the last few days in the list archives.
>Axel Kohlmeyer akohlmey_at_cmm.chem.upenn.edu http://www.cmm.upenn.edu
> Center for Molecular Modeling -- University of Pennsylvania
>Department of Chemistry, 231 S.34th Street, Philadelphia, PA 19104-6323
>tel: 1-215-898-1582, fax: 1-215-573-6233, office-tel: 1-215-898-5425
>If you make something idiot-proof, the universe creates a better idiot.
This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:49:44 CST