Normally, wesupply the full path for the mkl libraries, e.g. /opt/intel/mkl/9.0/....../libmkl_lapack.a. If you want the -l mechanism to work, you must set the MKL directory path with a preceding -L, or, possibly, make sure that you have run the mklvars path setting script. It's better, when using ifort or icc, to use the -openmp option to have the compiler take care implicitlyof libguide and libpthread. This would help avoid confusion about whether the libguide in MKL or ifort /lib directories will be in use.
I wouldn't say all of this is obvious; IMHO the MKL release notes cover the gcc situation OK but fall a little short on Fortran compilers.
I don't know anyone who uses Mac-32, but one would expect the -L/-l mechanism to work the same on all platforms.
Most of the people I work with avoid the default placement of MKL library directories, and some have requested a change to make more uniformity between Intel compiler and library tools, so I won't try to guess where your MKL libraries are.
