[MacPorts] #71068: R build fails due to g95 dependency, despite specifying gcc
MacPorts
noreply at macports.org
Fri Oct 11 07:02:34 UTC 2024
#71068: R build fails due to g95 dependency, despite specifying gcc
------------------------+--------------------
Reporter: klausness | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.10.2
Resolution: | Keywords: R g95
Port: R |
------------------------+--------------------
Comment (by barracuda156):
Replying to [comment:9 Alex11N]:
> Adding a probably redundant data point, I have ''exactly'' the same
problem on Sonoma 14.7 using the latest macports (2.10.2), Xcode (16.0)
and the CLTs.
>
> macports gcc is 14.2.0_3+stdlib_flag (active); macports llvm suites are:
llvm-16 @16.0.6_1 (active), llvm-18 @18.1.8_0 (active). llvm18 rebuilt
successfully last night from the latest macports update.
>
> The g95 roadblock is still persistent of course. I made the daft mistake
of uninstalling R, so will now have to get the precompiled version from
r-projects.org. That also means downloading a whole stack of libraries
again. This is all a bit frustrating.
>
> As a final comment, there's absolutely NO WAY that I'm installing 15.0.x
Sequoia on this current Mac (2019 19,2 i7 machine).
I am not sure why everyone keeps installing a semi-broken Xcode 16 when
the native Xcode 15 would have worked perfectly fine, but the fix for R it
trivial: just change Darwin 23 to Darwin 22 in the code chunks I
referenced above. So that gcc14 is used.
However, that gonna require building R stuff from source.
MacPorts should have informed users to avoid Xcode 16 on Sonoma. And as
long as buildbots use one Xcode and end-users use another, incompatible
one, there is no general fix for the issue.
--
Ticket URL: <https://trac.macports.org/ticket/71068#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list