[MacPorts] #44029: bitcoin: future versions in jeopardy of having MacPorts support dropped
#44029: bitcoin: future versions in jeopardy of having MacPorts support dropped ----------------------+-------------------------------- Reporter: vergus@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Keywords: | Port: ----------------------+-------------------------------- The latest bitcoin development versions no longer compile with MacPorts and the lead bitcoin tech has stated: RE: plan of action: the plan of action will be to drop support for MacPorts unless somebody using MacPorts steps forward and volunteers to fix things as they break. I used to use MacPorts, but have switched to brew. See this github issue for context and full details of the build issues with MacPorts: https://github.com/bitcoin/bitcoin/issues/3228#issuecomment-45808064 -- Ticket URL: <https://trac.macports.org/ticket/44029> MacPorts <http://www.macports.org/> Ports system for OS X
#44029: bitcoin: future versions in jeopardy of having MacPorts support dropped -----------------------+------------------------ Reporter: vergus@… | Owner: easieste@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: Port: bitcoin | -----------------------+------------------------ Changes (by mf2k@…): * cc: easieste@… (removed) * owner: macports-tickets@… => easieste@… * port: => bitcoin Comment: In the future, please fill in the Port field. -- Ticket URL: <https://trac.macports.org/ticket/44029#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44029: bitcoin: future versions in jeopardy of having MacPorts support dropped -----------------------+------------------------ Reporter: vergus@… | Owner: easieste@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: wontfix | Keywords: Port: bitcoin | -----------------------+------------------------ Changes (by easieste@…): * status: new => closed * resolution: => wontfix Comment: In the ensuing discussion, it seems that the following resolves the problem. {{{ ok, after what @neverpanic said and some googling I figured out that I had to do port select --set gcc none to reset clang++ as the default compiler. the linking errors disappeared after that. }}} In summary, this was a problem with how the bitcoin developers were using MacPorts. We can probably do better in our bitcoin portfile to detect the problematic situation, but I am closing as 'wontfix' for now. Please re- open with additional information if we need additional action on the MacPorts side. -- Ticket URL: <https://trac.macports.org/ticket/44029#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#44029: bitcoin: future versions in jeopardy of having MacPorts support dropped -----------------------+------------------------ Reporter: vergus@… | Owner: easieste@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: wontfix | Keywords: Port: bitcoin | -----------------------+------------------------ Comment (by vergus@…): FYI, apparently the bitcoin devs didn't get enough feedback, so they have dropped support for MacPorts and removed all mentions of it from the documentation. -- Ticket URL: <https://trac.macports.org/ticket/44029#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#44029: bitcoin: future versions in jeopardy of having MacPorts support dropped -----------------------+------------------------ Reporter: vergus@… | Owner: easieste@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: wontfix | Keywords: Port: bitcoin | -----------------------+------------------------ Comment (by cal@…): I don't understand what their problem was. The ticket mentioned above wasn't a problem with MacPorts, but a C++ library incompatibility problem – which we all have to deal with. I even took the time and explained the problem in greater detail. I also saw the change and pull request removing the MacPorts docs and didn't see a good reason (imo) to do so given in the pull request – especially no technical reason. If the bitcoin developers choose to drop support for MacPorts, that is entirely their right to do, but I really don't understand their rationale. -- Ticket URL: <https://trac.macports.org/ticket/44029#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#44029: bitcoin: future versions in jeopardy of having MacPorts support dropped -----------------------+------------------------ Reporter: vergus@… | Owner: easieste@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: wontfix | Keywords: Port: bitcoin | -----------------------+------------------------ Comment (by vergus@…): I think this misguided comment from the lead dev sums it up: https://github.com/bitcoin/bitcoin/pull/4917#issuecomment-55602501 "ACK on dropping mention of MacPorts, brew seems to have won the package-manager-on-OSX war." -- Ticket URL: <https://trac.macports.org/ticket/44029#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts