Opened 5 years ago

Closed 5 years ago

#60384 closed defect (fixed)

Failed py37-mayavi installation on maxos 10.14.6

Reported by: DanyPPage Owned by: jjstickel (Jonathan Stickel)
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: Cc:
Port: py-mayavi

Description

I just installed the macos update to 10.14.6, updated the ports, upgraded all the outdated ones and mayavi failed to build. The log file (attached) says it doesn't find vtk , but I do have it installed (with port)

Attachments (1)

main.log​ (279.0 KB) - added by DanyPPage 5 years ago.

Download all attachments as: .zip

Change History (8)

Changed 5 years ago by DanyPPage

Attachment: main.log​ added

comment:1 Changed 5 years ago by jmroot (Joshua Root)

Owner: set to jjstickel
Port: py-mayavi added; py37-mayavi removed
Status: new → assigned

comment:2 Changed 5 years ago by jmroot (Joshua Root)

It's saying that you have to install vtk with the python37 variant.

comment:3 in reply to:  2 Changed 5 years ago by jjstickel (Jonathan Stickel)

Replying to jmroot:

It's saying that you have to install vtk with the python37 variant.

Indeed, that is probably what is stopping the build. Can you provide the output of port installed vtk? However, the recent update of vtk to 8.2 has broken the python components (see #60367). I'll post here when that is fixed.

comment:4 Changed 5 years ago by DanyPPage

It is still broken once I have re-installed vkt with python37 variant.

% port installed vtk The following ports are currently installed:

vtk @8.2.0_0+python37 (active)

comment:5 in reply to:  4 Changed 5 years ago by jjstickel (Jonathan Stickel)

Replying to DanyPPage:

It is still broken once I have re-installed vkt with python37 variant.

% port installed vtk The following ports are currently installed:

vtk @8.2.0_0+python37 (active)

Like I said, the vtk port (with pythonXX variants) is broken now. We all have to wait for that to be fixed.

Last edited 5 years ago by jjstickel (Jonathan Stickel) (previous) (diff)

comment:6 Changed 5 years ago by jjstickel (Jonathan Stickel)

This should be fixed now with ​https://github.com/macports/macports-ports/pull/6926.

comment:7 Changed 5 years ago by mf2k (Frank Schima)

Resolution: → fixed
Status: assigned → closed

changeset:271d37672d376a74408736692f13369616482955/macports-ports

Note: See TracTickets for help on using tickets.