Dear Valentin,

Thanks for the hint.  Changing the toolchain version to '' gave me

  Building with 'gcc'.  Warning: You are using gcc version
  '4.8.5-36)'. The version of gcc is not supported. The version currently
  supported with MEX is '6.3.x'. For a list of currently supported
  compilers see:
  https://www.mathworks.com/support/compilers/current_release.

so I added

  builddependencies = [('GCCcore', '6.3.0')]

GCC 6.3.x being the supported version for my MATLAB version.

I still get an error:

  make: *** [utils_uchar.mexa64.o] Error 255
  make: *** Waiting for unfinished jobs....
  mv -f spm_vol_utils.o  utils_int_s.mexa64.o
  Building with 'gcc'.
  MEX completed successfully.
  mv -f spm_vol_utils.o  utils_schar.mexa64.o
  Building with 'gcc'.
  MEX completed successfully.
  Building with 'gcc'.
  The command '/trinity/shared/easybuild/software/GCCcore/6.3.0/bin/gcc' exited 
with a return value '0'
  Building with 'gcc'.
  MEX completed successfully.
  mv -f spm_vol_utils.o  utils_float.mexa64.o
  mv -f spm_vol_utils.o  utils_ushort.mexa64.o
  Building with 'gcc'.
  The command '/trinity/shared/easybuild/software/GCCcore/6.3.0/bin/gcc' exited 
with a return value '0'
  make: *** [utils_double_s.mexa64.o] Error 255
  Building with 'gcc'.
  The command '/trinity/shared/easybuild/software/GCCcore/6.3.0/bin/gcc' exited 
with a return value '0'
  mv -f spm_vol_utils.o  utils_ushort_s.mexa64.o
  Building with 'gcc'.
  The command '/trinity/shared/easybuild/software/GCCcore/6.3.0/bin/gcc' exited 
with a return value '0'
  mv: cannot stat ‘spm_vol_utils.o’: No such file or directory

This seems however not to be Easybuild-related.

Cheers,

Loris

Valentin Plugaru <[email protected]> writes:

> Dear Loris,
>
> What if you change the dummy toolchain version to '' , e.g.:
>
> toolchain = {'name': 'dummy', 'version': ''}
>
> See https://github.com/easybuilders/easybuild-framework/issues/2318
> and
> https://easybuild.readthedocs.io/en/latest/Concepts_and_Terminology.html?#dummy-toolchain
>
> Kind regards,
> Valentin
>
> On 2019-04-09 16:21, Loris Bennett wrote:
>> Loris Bennett <[email protected]> writes:
>>
>>> Hi,
>>>
>>> I want to write an easyconfig for SPM
>>>
>>>    https://www.fil.ion.ucl.ac.uk/spm/software/spm12/
>>>
>>> which is a GPL toolbox for MATLAB.  It comprises a bunch of MATLAB
>>> files, both in the top-level directory and in various subdirectories.  In
>>> addition there is a 'src' subdirectory, which contains some C files and
>>> a makefile, whose install step just copies the binaries to the top-level
>>> and to some other subdirectories.
>>>
>>> Which easyblock might be most appropriate for this scenario?  I looked
>>> at 'MakeCp', but this has 'files_to_copy' as a mandatory parameter.  As
>>> I want to copy everything, this made me think that there might be an
>>> more suitable easyblock.
>>>
>>> Any thoughts?
>> I have
>>
>>    easyblock = 'MakeCp'
>>
>>    name = 'SPM'
>>    version = '12'
>>
>>    homepage = 'https://www.fil.ion.ucl.ac.uk/spm/'
>>    description = """Statistical Parametric Mapping refers to the 
>> construction and assessment of
>>    spatially extended statistical processes used to test hypotheses about
>>    functional imaging data. These ideas have been instantiated in software 
>> that is
>>    called SPM."""
>>
>>    toolchain = {'name': 'dummy', 'version': 'dummy'}
>>
>>    source_urls = 
>> ['http://www.fil.ion.ucl.ac.uk/spm/download/restricted/eldorado']
>>    sources = ['%(namelower)s%(version_major)s.zip']
>>    checksums = 
>> ['02bb2def8a091c9c1ceaea0194fb1014e9b435a937a0efa618d9bef15a9c53b4']
>>
>>    dependencies = [('MATLAB', '2018b')]
>>
>>    start_dir = 'src'
>>
>>    files_to_copy = ['*']
>>
>>    sanity_check_paths = {
>>        'files': ["spm_add.m", "spm_zeros.m"],
>>        'dirs': ["toolbox", "tpm"]
>>    }
>>
>>    moduleclass = 'bio'
>>
>>    modextravars = { 'MATLABPATH':  '.',
>>                     'PATH': 'bin',
>>    }
>>
>> but the build is failing with
>>
>>    mex -O -largeArrayDims -c spm_vol_utils.c -DSPM_UNSIGNED_CHAR
>>    make: mex: Command not found
>>
>> There is no indication in the log file of MATLAB being loaded, so I
>> guess I'm doing some thing wrong and just specifying MATLAB as a
>> dependency is not enough.
>>
>> Does anyone have an idea?
>>
>> Cheers,
>>
>> Loris
>>
-- 
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin         Email [email protected]

Reply via email to