> I just updated to rev1024 and came in contact with the new
> check_installation routine in spm.m
I had hoped that this one would flag up a lot of the installation problems
that people have - particularly those due to files being corrupted by WinZip.
>
> I compiled the mexfiles with my matlab-version (2007b) and everything
> worked fine.
>
> The problem is, I support quite some computers with spm via nfs-export and
> there are some other matlab-versions installed on those computers. With the
> last spm5-version (958) I had to recompile the mexfiles but could use all
> matlab-version (>=7) after that recompile.
>
> Since 1048 I only can use matlab 2007(a&b).
>
> Doing the check_installation manually with my 958 version and matlab2006a
> also
>
> provides an error:
> >> spm_atranspa(1)
>
> ??? Invalid
> MEX-file '/misc/spm/spm5_rev1048/spm_atranspa.mexglx':
> /misc/spm/spm5_rev1048/spm_atranspa.mexglx: undefined symbol:
> mxCreateDoubleMatrix_700.
>
> So the question is:
> -Was I just lucky before that all versions of matlab could cope with the
> mexfiles compiled with 2007b?
> -or is the test provided just a bit too sensitive?
I think it is because your test is using the spm5_rev1048/spm_atranspa.mexglx
rather than the spm5_rev958/spm_atranspa.mexglx . Check your MATLABPATH.
Because the updates are actually almost as big as the full installation and
because so many people were confusing the updates with the full release, I
tried to sneak in a full installation of SPM5 in these updates without anyone
noticing. This would have over-written any mexglx files that you may have
compiled yourself.
Best regards,
-John
|