Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

idb: libpostoffice

roddur
Beginner
524 Views
libPostoffice.so is not activated when calling idb either by "source"ing ifortvars or idbvars.
the only way is export the file in LD_LIBRARY_PATH.
why?
0 Kudos
5 Replies
Hubert_H_Intel
Employee
524 Views
Quoting - roddur
libPostoffice.so is not activated when calling idb either by "source"ing ifortvars or idbvars.
the only way is export the file in LD_LIBRARY_PATH.
why?

The only thing you need to do is to source the compiler script iccvars.(c)sh or ifortvars.(c)sh which sets up all compiler, debugger and libraries environment variables. All required runtime libs are then included in LD_LIBRARY_PATH.
E.g.:
$ source /opt/intel/Compiler/11.1/059/bin/iccvars.sh ia32
$icc -V
Intel C Compiler Professional for applications running on IA-32, Version 11.1 Build 20091012 Package ID: l_cproc_p_11.1.059
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

$ idbc -version
Intel Debugger for applications running on IA-32, Version 11.1, Build [1.2097.2.295]

It seems it's an older version you are using since libPostoffice.so is no longer included with the Compiler

How did you notice that libPostoffice.so is missing and required for using idb?
Hubert.
0 Kudos
TimP
Honored Contributor III
524 Views
Checking earlier posts, I find libPostoffice mentioned only in connection with the one Intel64 compiler version where libraries required for idb were omitted. So you should look to see if you are using that version.
0 Kudos
Kevin_D_Intel
Employee
524 Views

Its an earlier 11.0 defect; the earlier post is (here). DPD200110439. Its visible via ldd or iidb:

$ iidb
iidb: error while loading shared libraries: libPostOffice.so: cannot open shared object file: No such file or directory
0 Kudos
roddur
Beginner
524 Views
Not really, as you can see:
in my bashrc, i have:

# User specific aliases and functions
source /opt/intel/Compiler/11.1/056/bin/ifortvars.sh ia32

$ which ifort
/opt/intel/Compiler/11.1/056/bin/ia32/ifort

$ ifort --version
ifort (IFORT) 11.1 20090827
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

$ uname -a
Linux roddur 2.6.30.9-90.fc11.i686.PAE #1 SMP Sat Oct 17 11:24:32 EDT 2009 i686 i686 i386 GNU/Linux

$ iidb
iidb: error while loading shared libraries: libPostOffice.so: cannot open shared object file: No such file or directory


It may be caused by the fact that fc11 not supported fully, but what is more confusing is if I simply put
$ export LD_LIBRARY_PATH=/opt/intel/Compiler/11.1/056/idb/lib/ia32/
it works fine, suggesting idb/lib is not activated by ifortvars.

$ iidb
Intel Debugger for applications running on IA-32, Version 11.1, Build [1.2097.2.270]
FOR NON-COMMERCIAL USE ONLY


(idb) q

0 Kudos
Hubert_H_Intel
Employee
524 Views

Its an earlier 11.0 defect; the earlier post is (here). DPD200110439. Its visible via ldd or iidb:

$ iidb
iidb: error while loading shared libraries: libPostOffice.so: cannot open shared object file: No such file or directory

You should call the debugger by it's driver start script idb only, not the debugger executable iidb. This sets the library paths correctly.
E.g.:
-bash-3.1$ source /opt/intel/Compiler/11.1/059/bin/ifortvars.sh intel64
-bash-3.1$ iidb
iidb: error while loading shared libraries: libPostOffice.so: cannot open shared object file: No such file or directory
-bash-3.1$ idb
...
and the idb starts.
Hubert.
0 Kudos
Reply