Hi Emanuel,

thank you for your answer. The relevant line from "ldd hybridization" output is probably

libalps.so.2 => /data/sw/alps/lib/libalps.so.2 (0x00002ac9a097d000)

The libalps.so.2 is link to libalps.so.2.0.0rc2. That is, alps version 2.0.2. Is it wrong? What is the correct version? Just in case, the full output from ldd is attached below. Thanks once again,

Pavel

libz.so.1 => /lib64/libz.so.1 (0x00002ac9a0869000) libalps.so.2 => /data/sw/alps/lib/libalps.so.2 (0x00002ac9a097d000) libboost.so => /data/sw/alps/lib/libboost.so (0x00002ac9a117d000) libmpi_cxx.so.0 => /usr/openmpi/lib/libmpi_cxx.so.0 (0x00002ac9a14fe000) libmpi.so.0 => /usr/openmpi/lib/libmpi.so.0 (0x00002ac9a1624000) libopen-rte.so.0 => /usr/openmpi/lib/libopen-rte.so.0 (0x00002ac9a17ea000) libopen-pal.so.0 => /usr/openmpi/lib/libopen-pal.so.0 (0x00002ac9a196a000) libdl.so.2 => /lib64/libdl.so.2 (0x00002ac9a1ae4000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00002ac9a1be9000) libutil.so.1 => /lib64/libutil.so.1 (0x00002ac9a1cff000) libhdf5.so.6 => /usr/local/hdf5/lib/libhdf5.so.6 (0x00002ac9a1e02000) libhdf5_hl.so.6 => /usr/local/hdf5/lib/libhdf5_hl.so.6 (0x00002ac9a21a1000) libmkl_lapack.so => /opt/intel/Compiler/11.1/064/mkl/lib/em64t/libmkl_lapack.so (0x00002ac9a22ce000) libmkl_intel_lp64.so => /opt/intel/Compiler/11.1/064/mkl/lib/em64t/libmkl_intel_lp64.so (0x00002ac9a2f23000) libmkl_intel_thread.so => /opt/intel/Compiler/11.1/064/mkl/lib/em64t/libmkl_intel_thread.so (0x00002ac9a3324000) libmkl_core.so => /opt/intel/Compiler/11.1/064/mkl/lib/em64t/libmkl_core.so (0x00002ac9a4387000) libguide.so => /opt/intel/Compiler/11.1/064/lib/intel64/libguide.so (0x00002ac9a45c7000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ac9a476d000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ac9a4886000) libm.so.6 => /lib64/libm.so.6 (0x00002ac9a4a84000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ac9a4bda000) libc.so.6 => /lib64/libc.so.6 (0x00002ac9a4ce7000) libimf.so => /opt/intel/Compiler/11.1/064/lib/intel64/libimf.so (0x00002ac9a4f28000) libsvml.so => /opt/intel/Compiler/11.1/064/lib/intel64/libsvml.so (0x00002ac9a52ba000) libintlc.so.5 => /opt/intel/Compiler/11.1/064/lib/intel64/libintlc.so.5 (0x00002ac9a54d0000) /lib64/ld-linux-x86-64.so.2 (0x00002ac9a074d000)

Hi Pavel,

this looks like a problem with the dynamic libraries. It may be because hybridization2 is dynamically linked to an older ALPS library. Could you please check if your library path is set correctly (ldd hybridization2 under Linux)?

Emanuel

On Apr 11, 2012, at 4:44 PM, august@fzu.cz wrote:

...

Dear all,

I am trying to use the CT-HYB code from the directory

alps/applications/dmft/qmc/hybridization2

So, I have enabled the ALPS_BUILD_NGS option using ccmake and recompiled. But when I try to run the "hybridization" executable using the provided minimal configuration file, it crashes on

symbol lookup error: undefined symbol: _ZN4alps9mcoptionsC1EiPPc

I provided both the Umatrix and the hybridization function F_1 file.

Could you please tell me what to do? Thank you!

Pavel Augustinsky