Changes between Initial Version and Version 1 of Ticket #59673, comment 6


Ignore:
Timestamp:
Jan 12, 2020, 8:31:39 PM (5 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #59673, comment 6

    initial v1  
    1 It is an actual issue in that an actual error message that occurs when attempting to install a port which should not occur. I don't know what the solution is. [comment:1 Josh claimed] that there was no valid use case for including both portgroups, so I'm trying to get data from those who have included both portgroups about why that was necessary, so that we can decide what the correct fix is: either removing one or the other portgroup from the ports, or allowing the portgroups to coexist somehow.
     1It is an actual issue in that an actual error message occurs when attempting to install a port which should not occur. I don't know what the solution is. [comment:1 Josh claimed] that there was no valid use case for including both portgroups, so I'm trying to get data from those who have included both portgroups about why that was necessary, so that we can decide what the correct fix is: either removing one or the other portgroup from the ports, or allowing the portgroups to coexist somehow.
    22
    33The cmake portgroup is for configuring using cmake and building using make. The python portgroup is for disabling the configure phase and building using setup.py. Which of these does the port want? Looking at a [https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/107125/steps/install-port/logs/stdio build log for py37-onnx], I see that it has not used a configure phase and it has built using setup.py. This suggests to me that you're not actually using the cmake portgroup. Did you try without it?