#44029 closed defect (wontfix)
bitcoin: future versions in jeopardy of having MacPorts support dropped
| Reported by: | vergus@… | Owned by: | easye |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.0 |
| Keywords: | Cc: | sami.laine@… | |
| Port: | bitcoin |
Description
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
Change History (5)
comment:1 Changed 10 years ago by mf2k (Frank Schima)
| Cc: | easieste@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to easieste@… |
| Port: | bitcoin added |
comment:2 Changed 10 years ago by easye
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
In the ensuing discussion, it seems that the following resolves the problem.
[…] 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.
comment:3 Changed 10 years ago 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.
comment:4 Changed 10 years ago by neverpanic (Clemens Lang)
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.
comment:5 Changed 10 years ago 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."
In the future, please fill in the Port field.