Hi Andreas,
You should try and collect a debug log, and figure out why the sanity check is
failing.
But, I think I already know. By default, EasyBuild will try to import the
module after building/installing it, as a sanity check.
For that, it assumes that the module name to import is the same of the name of
the package, which is probably not correct for BioPython.
You can fix that by explicitly specifying the correct module name, using
"options = {'modulename': 'foo'} " in the easyconfig file.
Another example of a Python package that requires this is pyTables, see
https://github.com/hpcugent/easybuild-easyconfigs/blob/master/easybuild/easyconfigs/p/pyTables/pyTables-2.4.0-ictce-4.1.13-Python-2.7.3.eb
.
regards,
Kenneth
On 27 May 2013, at 10:29, Andreas Panteli wrote:
> Dear all,
>
> please first let me introduce my self. I am Andreas Panteli and I recently
> joined the operations team at the Cyprus Institute.
>
> I am currently working on importing some bioinformatics packages into
> Easybuild and I am facing a problem with Biopython. To install Biopython I
> used the "PythonPackage" generic easyblock in my config file.
>
> The problem is that the installation process breaks at the sanity check step,
> with the following error:
>
> ERROR: EasyBuild encountered an exception (at easybuild/tools/build_log.py:69
> in caller_info): autoBuild Failed (last 300 chars): EasyBuild crashed with an
> error (at easybuild/tools/build_log.py:69 in caller_info): Sanity check for
> Biopython failed!
>
> Any help is welcome.
>
> Thank you,
>
> Best regards,
>
> Andreas Panteli
> HPC Operations
> CaSToRC, the Cyprus Institute
