Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #12210 > unrolled thread

Re: python3-arcus only builds for python 3.8 despite pybuild

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: python3-arcus only builds for python 3.8 despite pybuild Christoph Berg <myon@debian.org> - 2020-01-19 22:20 +0100
    Re: python3-arcus only builds for python 3.8 despite pybuild Christoph Berg <myon@debian.org> - 2020-01-20 13:20 +0100

#12210 — Re: python3-arcus only builds for python 3.8 despite pybuild

Re: Gregor Riepl 2020-01-17 <747a6f03-b489-5637-face-e1b5f4fe265b@gmail.com>
> Does someone have an idea why pybuild doesn't produce python3.7 and 3.8
> modules, and why autopkgtest only installs python3.7 for the test dependency?

I've had another look at the build log. It does build the modules for
both versions, but then the install target installs for 3.8 during the
3.7 install run:

[100%] Built target python_module_Arcus
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.8/build“ wird verlass
en
/usr/bin/cmake -E cmake_progress_start /srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.8/bu
ild/CMakeFiles 0
make -f CMakeFiles/Makefile2 preinstall
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.8/build“ wird betrete
n
make[2]: Für das Ziel „preinstall“ ist nichts zu tun.
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.8/build“ wird verlass
en
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/python3.8/site-packages/Arcus
.so
-- Set runtime path of "/srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/python3.8/site-packa
ges/Arcus.so" to ""
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/libArcus.so.
1.1.0
[...]
ArcusConfigVersion.cmake
make[1]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.8/build“ wird verlass
en
I: pybuild base:217: dh_auto_install --buildsystem=cmake --builddirectory="/srv/debian/3d/libarc
us/libarcus/.pybuild/cpython3_3.7/build" --destdir="/srv/debian/3d/libarcus/libarcus/debian/tmp"
 --
        cd .pybuild/cpython3_3.7/build && make -j4 install DESTDIR=/srv/debian/3d/libarcus/libar
cus/debian/tmp AM_UPDATE_INFO_DIR=no
make[1]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build“ wird betrete
n
/usr/bin/cmake -S/srv/debian/3d/libarcus/libarcus -B/srv/debian/3d/libarcus/libarcus/.pybuild/cp
ython3_3.7/build --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/bu
ild/CMakeFiles /srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build/CMakeFiles/progress.
marks
make -f CMakeFiles/Makefile2 all
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build“ wird betrete
n
[...]
[100%] Built target python_module_Arcus
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build“ wird verlassen
/usr/bin/cmake -E cmake_progress_start /srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build/CMakeFiles 0
make -f CMakeFiles/Makefile2 preinstall
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build“ wird betreten
make[2]: Für das Ziel „preinstall“ ist nichts zu tun.
make[2]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build“ wird verlassen
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/python3.8/site-packages/Arcus.so                    <---------- !!!
-- Set runtime path of "/srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/python3.8/site-packages/Arcus.so" to ""
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/libArcus.so.1.1.0
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/libArcus.so.3
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/libArcus.so
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/include/Arcus/Socket.h
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/include/Arcus/SocketListener.h
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/include/Arcus/Types.h
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/include/Arcus/MessageTypeStore.h
-- Up-to-date: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/include/Arcus/Error.h
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/include/Arcus/ArcusExport.h
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Arcus/Arcus-targets.cmake
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Arcus/Arcus-targets-none.cmake
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Arcus/ArcusConfig.cmake
-- Installing: /srv/debian/3d/libarcus/libarcus/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Arcus/ArcusConfigVersion.cmake
make[1]: Verzeichnis „/srv/debian/3d/libarcus/libarcus/.pybuild/cpython3_3.7/build“ wird verlassen
   dh_install -O--buildsystem=pybuild

Is that a failure in pybuild, cmake or dh-python?

Christoph

[toc] | [next] | [standalone]

#12211

Re: To Gregor Riepl 2020-01-19 <20200119211205.GA69852@msg.df7cb.de>
> Is that a failure in pybuild, cmake or dh-python?

(Continued on #debian-python, and in #949377.)

Christoph

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web