Re: Linux build with Python 3.9
Ralf Gommers <[email protected]> Wed, 24 May 2023 10:25:49 +0200
| Newsgroups | gmane.comp.python.scientific.devel |
|---|---|
| Message-ID | <CABL7CQiJspqbfPQ5hHXGeEOf8y8hkm6aWpQ0uejbFshu0Viobg@mail.gmail.com> |
On Wed, May 24, 2023 at 10:08 AM Andrew Nelson <[email protected]> wrote: > Is the venv located in the scipy source directory? Try installing the venv > elsewhere. > That should fix it indeed. But also, this error should not be happening anymore with in-tree venvs after https://github.com/scipy/scipy/pull/18006 and this is the first report I've seen since that. Chris, if you see this error with an up-to-date main branch, can you please open an issue with a reproducer and assign it to me? The `export LD_LIBRARY_PATH=/usr/local/lib` part is also an indication that something is off, that should never be needed. I'll have a look at removing that from the CI job. Cheers, Ralf > On Wed, May 24, 2023, 07:41 Christoph Baumgarten < > [email protected]> wrote: > >> >> Hi all, >> >> I wanted to replicate a test failure in the Meson build "Linux - 32 bit" >> of my PR #17955. I tried to follow the steps in the following yml file >> (L335): >> >> scipy/linux_meson.yml at main · scipy/scipy · GitHub >> <https://github.com/scipy/scipy/blob/main/.github/workflows/linux_meson.yml> >> >> So essentially I did the following: >> >> - pull docker image and run it >> - clone my repository >> - run "python3.9 tools/openblas_support.py" >> - copy the downloaded files to the indicated directories >> - set PKG_CONFIG_PATH >> - create venv and install packages >> >> These steps worked fine. When I then run "python dev.py build", I get an >> error: >> >> scipy/meson.build:48:9: ERROR: Tried to form an absolute path to a dir in >> the source tree. You should not do that but use relative paths instead, for >> directories that are part of your project. [...] >> >> The detailed output is at the end of the email. The last two lines in the >> yml file are: >> >> python dev.py build && \ >> LD_LIBRARY_PATH=/usr/local/lib python dev.py test >> >> I first wanted to build scipy before running certain tests. I am not sure >> if the error is related to not using LD_LIBRARY_PATH, I just ran "python >> dev.py build". >> >> I hope that someone can help. Thanks >> >> Regards >> >> Christoph >> >> (test) [root@c73b212ff29a scipy]# python dev.py build >> meson setup /home/scipy/build --prefix /home/scipy/build-install >> The Meson build system >> Version: 1.1.0 >> Source dir: /home/scipy >> Build dir: /home/scipy/build >> Build type: native build >> Project name: SciPy >> Project version: 1.11.0.dev0 >> C compiler for the host machine: cc (gcc 10.2.1 "cc (GCC) 10.2.1 20210130 >> (Red Hat 10.2.1-11)") >> C linker for the host machine: cc ld.bfd 2.35-5 >> C++ compiler for the host machine: c++ (gcc 10.2.1 "c++ (GCC) 10.2.1 >> 20210130 (Red Hat 10.2.1-11)") >> C++ linker for the host machine: c++ ld.bfd 2.35-5 >> Cython compiler for the host machine: cython (cython 0.29.33) >> Host machine cpu family: x86 >> Host machine cpu: i686 >> Compiler for C supports arguments -Wno-unused-but-set-variable: YES >> Compiler for C supports arguments -Wno-unused-function: YES >> Compiler for C supports arguments -Wno-conversion: YES >> Compiler for C supports arguments -Wno-misleading-indentation: YES >> Compiler for C supports arguments -Wno-incompatible-pointer-types: YES >> Library m found: YES >> Fortran compiler for the host machine: gfortran (gcc 10.2.1 "GNU Fortran >> (GCC) 10.2.1 20210130 (Red Hat 10.2.1-11)") >> Fortran linker for the host machine: gfortran ld.bfd 2.35-5 >> Compiler for Fortran supports arguments -Wno-conversion: YES >> Checking if "-Wl,--version-script" : links: YES >> Program cython found: YES (/home/scipy/test/bin/cython) >> Program python3 found: YES (/home/scipy/test/bin/python) >> Found pkg-config: /usr/bin/pkg-config (0.27.1) >> Program pythran found: YES (/home/scipy/test/bin/pythran) >> Run-time dependency threads found: YES >> >> scipy/meson.build:48:9: ERROR: Tried to form an absolute path to a dir in >> the source tree. >> You should not do that but use relative paths instead, for >> directories that are part of your project. >> >> _______________________________________________ >> SciPy-Dev mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> https://mail.python.org/mailman3/lists/scipy-dev.python.org/ >> Member address: [email protected] >> > _______________________________________________ > SciPy-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/scipy-dev.python.org/ > Member address: [email protected] > _______________________________________________ SciPy-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: [email protected]