python-pivy build fails (freecad dependency)

  • Done
  • quality assurance status badge
Details
2 participants
  • Buttons Presser
  • Guillaume Le Vaillant
Owner
unassigned
Submitted by
Buttons Presser
Severity
normal
B
B
Buttons Presser wrote on 1 May 17:18 +0200
(address . bug-guix@gnu.org)
87cyq58ss9.fsf@disroot.org
Dear guix community,

My local python-pivy build fails and there is no longer a working substitute available.

The build log is attached (q806khpbab7n9nk9i6ynbfhm85gd48-python-pivy-0.6.5.drv.gz).

I suspect that python-pivy stoped building after recent patches to coin3d - https://issues.guix.gnu.org/70305

Looks like this is an issue with paths in the python-pivy install scripts (build phase: python setup.py). Specifically in its swig command which probably misses some paths to soqt and coin3D.

I was trying to fix and upgrade the python-pivy before because the current version is 0.6.5 is old and some features of freecad was not working properly - https://issues.guix.gnu.org/70258.I guess there should be a patch to the python-pivy cmake config that can fix the paths to soqt and coin3D but I am not familiar with cmake and thus far did not find a solution.

Kind regards,
BP
B
B
Buttons Presser wrote on 1 May 17:25 +0200
(address . 70698@debbugs.gnu.org)
87zft97dvj.fsf@disroot.org
Forgot to add the guix version for this issue:

guix describe ->

guix 7d4ae2f
branch: master
commit: 7d4ae2fca723114fb1df56de33b82177fbc4d0a6
G
G
Guillaume Le Vaillant wrote on 15 May 14:18 +0200
(name . Buttons Presser)(address . buttonspresser@disroot.org)(address . 70698-done@debbugs.gnu.org)
87frujl14j.fsf@kitej
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCZkSoDA8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9rhQD7BAMZtc6R9TkReb/I57oVdF+2bT86LO2d++Y6
eEFLMuUA/AiJZQShQlglZMCEXnaWWqDKRkTCzXJu7+yry73ka4OY
=4l3R
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 70698@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70698
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch