First of all, the BLAS and LAPACK performance is not critical for Meep (it is only used for Harminv, which is only run at the end of the simulation and not at every time step so it is not speed-critical).
Second, if one of the configure tests is not giving you the expected results then the right thing to do is to look at the config.log file (automatically generated every time you run configure). If you search config.log for the offiending line (e.g. search it for libmkl_em64t) you will see the *exact* linker error message that caused linking to fail. Third, linking the Intel MKL libraries is tricky unless you are compiling Meep itself with the Intel compilers, as MKL (if I recall correctly) requires some additional libraries to be linked that are linked by default when you use icc but must be specified explicitly (e.g. by adding them to LIBS) if you use some other compiler. Fourth, note that you are linking the em64t version of MKL (i.e. for x86_64). In order to link this, in addition to the consideration above, you need to make sure you are using a 64-bit compiler (e.g. gcc with the -m64 option) and *all* of your code and libraries for Meep needs to be compiled in 64-bit mode. Cordially, Steven G. Johnson _______________________________________________ meep-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
