Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29286 Discussions

ScaLAPACK benchmark doesn't create output TXT files

Dusan_Z_
Beginner
‎12-11-2006 12:57 PM
371 Views
Hello,

I am starting to work with ScaLAPACK library and I am trying to make and execute the ScaLAPACK tests, as given in Intel Cluster Toolkit Tutorial, on page 74 in chapter: "Getting started with the Intel Math Kernel Library Cluster Edition".
I am following the instructions from the Tutorial: I go to

/opt/intel/ict/2.0/cmkl/8.0.1/tests/scalapack

and then type:

gmake libem64t F=intel90 mpi=intelmpi20 LIBdir=/opt/intel/ict/2.0/cmkl/8.0.1/lib/em64t

Gmake does its job, it compiles the source files and then sends out execution commands of built programs (for 4 nodes, I have 8) and everything seems fine. No error messages.

But, when I look for the output *.txt files in the teste/scalapack/source/TESTING directory, there isn't any. It is as if no output files were created during the execution of programs.

I am running the tests as root, so I think there shouldn't be any permission problems.

What can be done to solve the problem?
0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.