- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm having the following problems with the libguide library. I'm using the SERIAL version of the MKL blas and lapack libraries together with the threaded version of PARDISO v3.2 available from the developers.
I link all of them with the following commands (part of my Makefile) on a Clovertown machine:
FC := ifort -O3 -r8 -i8 -xT -traceback
LIBS := -L ../lib/x86_64 -lpardiso_INTEL_91_EM64T_P -lskit -lmkl_lapack -lmkl_em64t
HOMER: $(HOMER_Objects)
@echo Compiling HOMER for the $(shell arch) architecture ...
@$(FC) -module ../obj/ $^ $(LIBS) -openmp -o ../bin/HOMER
Then I run the program and everything works fine. But then, after about 4 hours computing using four threads the program stops and I get the following message:
OMP abort: Initializing libguide.so, but found libguide.so already initialized.
This may cause performance degradation and correctness issues.
Set environment variable KMP_DUPLICATE_LIB_OK=TRUE to ignore
this problem and force the program to continue anyway.
Please note that the use of KMP_DUPLICATE_LIB_OK is unsupported
and using it may cause undefined behavior.
For more information, please contact Intel Premier Support.
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libpthread.so.0 0000003C2E80C430 Unknown Unknown Unknown
libpthread.so.0 0000003C2E80C2CE Unknown Unknown Unknown
libguide.so 0000002A9588820E Unknown Unknown Unknown
I switched to the serial version of the MKL libraries to avoid this problem (after reading the MKL user guide), but now I do not know what to do, as I do not understand from where does the duplicate libguide.so come from ...
Somebody knows a solution?
Thanks in advance and greetings from Spain,
Miguel
I'm having the following problems with the libguide library. I'm using the SERIAL version of the MKL blas and lapack libraries together with the threaded version of PARDISO v3.2 available from the developers.
I link all of them with the following commands (part of my Makefile) on a Clovertown machine:
FC := ifort -O3 -r8 -i8 -xT -traceback
LIBS := -L ../lib/x86_64 -lpardiso_INTEL_91_EM64T_P -lskit -lmkl_lapack -lmkl_em64t
HOMER: $(HOMER_Objects)
@echo Compiling HOMER for the $(shell arch) architecture ...
@$(FC) -module ../obj/ $^ $(LIBS) -openmp -o ../bin/HOMER
Then I run the program and everything works fine. But then, after about 4 hours computing using four threads the program stops and I get the following message:
OMP abort: Initializing libguide.so, but found libguide.so already initialized.
This may cause performance degradation and correctness issues.
Set environment variable KMP_DUPLICATE_LIB_OK=TRUE to ignore
this problem and force the program to continue anyway.
Please note that the use of KMP_DUPLICATE_LIB_OK is unsupported
and using it may cause undefined behavior.
For more information, please contact Intel Premier Support.
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libpthread.so.0 0000003C2E80C430 Unknown Unknown Unknown
libpthread.so.0 0000003C2E80C2CE Unknown Unknown Unknown
libguide.so 0000002A9588820E Unknown Unknown Unknown
I switched to the serial version of the MKL libraries to avoid this problem (after reading the MKL user guide), but now I do not know what to do, as I do not understand from where does the duplicate libguide.so come from ...
Somebody knows a solution?
Thanks in advance and greetings from Spain,
Miguel
Link Copied
0 Replies
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page