"Loris Bennett" <loris.bennett-j/[email protected]>
writes:
> Hi,
>
> In an EC I am writing for Medaka 2.0.1 I have
>
> exts_list = [
> ('mappy', '2.29', {
> 'checksums':
> ['43dda2693c963152ddb5be9eac2b7ea0c943cba9becd79494a9f2b8804039a9a'],
> }),
> ...
>
> However, the installation of this extension fails with:
>
> gcc -fno-strict-overflow -DNDEBUG -g -O3 -Wall -O2 -ftree-vectorize
> -march=native -fno-math-errno -fPIC -O2 -ftree-vectorize -march=native
> -fno-math-errno -fPIC -O2 -ftree-vectorize -march=native -fno-math-errno
> -fPIC -I/trinity/shared/easybuild/software/FFTW/3.3.10-GCC-13.3.0/include
> -I/trinity/shared/easybuild/software/FlexiBLAS/3.4.4-GCC-13.3.0/include
> -I/trinity/shared/easybuild/software/FlexiBLAS/3.4.4-GCC-13.3.0/include/flexiblas
> -fPIC -I.
> -I/trinity/shared/easybuild/software/Python/3.12.3-GCCcore-13.3.0/include/python3.12
> -c python/mappy.c -o build/temp.linux-x86_64-cpython-312/python/mappy.o
> -DHAVE_KALLOC -msse4.1
> cc1: fatal error: python/mappy.c: No such file or directory
>
> I assume the missing file is supposed to be generated from
> 'python/mappy.pyx', which does exist, but for some reason this is not
> happening.
>
> Any ideas how to debug the issue?
As soon as I sent the above message, I poked about a bit an realised
that there was a 'python/mappy.pyx', from which Cython can generate a C
file. So I just added Cython to the list of build dependencies and Bob
was my uncle.
For the previous version of Medaka for which I wrote an EC which I am
using as a basis for the new one, the C file was contained explicitly,
so there was no need for Cython.
Sorry for the noise.
Cheers,
Loris
--
Dr. Loris Bennett (Herr/Mr)
FUB-IT, Freie Universität Berlin
