Back to the main page.
Bug 2495 - MEX file error during execution of ft_timelockanalysis
| Status | CLOSED FIXED |
| Reported | 2014-03-11 15:09:00 +0100 |
| Modified | 2014-05-14 20:08:48 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P5 blocker |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | 2452 |
| See also: |
Heidi - 2014-03-11 15:09:47 +0100
This is the full error message Matlab gives me when I'm using Matlab2011a via a Mentat cluster at the DCCN: ************************************************************************* Warning: trying to compile MEX file from /home/common/matlab/fieldtrip/utilities/private/mxSerialize.c > In utilities/private/mxSerialize at 35 In utilities/private/ft_preamble_provenance at 67 In ft_preamble at 54 In ft_timelockanalysis at 95 Warning: You are using gcc version "4.4.6". The version currently supported with MEX is "4.3.4". For a list of currently supported compilers see: http://www.mathworks.com/support/compilers/current_release/ mex: /home/common/matlab/fieldtrip/utilities/private/mxSerialize.c not a normal file or does not exist. Error using mex (line 206) Unable to complete successfully. Error using mxSerialize (line 44) could not locate MEX file for mxSerialize Error in ft_preamble_provenance (line 67) cfg.callinfo.inputhash{iargin} = CalcMD5(mxSerialize(tmparg)); Error in ft_preamble (line 54) evalin('caller', ['ft_preamble_' cmd]); Error in ft_timelockanalysis (line 95) ft_preamble provenance data ********************************************************************* In other words, ft_timelockanalysis has a bug in it now... (ft_preprocessing worked fine.) I've tried different combinations of Matlab and OS, but keep getting the same error. Help? (Might this have something to do with the fact that some MEX files have been changed today? --> http://code.google.com/p/fieldtrip/source/detail?r=9275 and http://code.google.com/p/fieldtrip/source/detail?r=9276)
Robert Oostenveld - 2014-03-11 15:24:58 +0100
Hi Heidi, Sorry for the inconvenience, my fault. I introduced the bug earlier this afternoon and I just fixed it. See http://code.google.com/p/fieldtrip/source/detail?r=9280