Changes between Initial Version and Version 1 of Ticket #60791, comment 3
- Timestamp:
- Aug 17, 2021, 3:08:40 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #60791, comment 3
initial v1 9 9 Next step was to see if there were any variants of `julia` that were still working, and that's when it dawned on me: the latest version of `julia` wants `gcc10`, but my "active" `gcc` was `mp-gcc5`. So, in retrospect, it seems understandable that the build would bomb out with ABI errors. 10 10 11 What I ended up doing was `sudo port select gcc mp-gcc9`, followed by `sudo port install julia +gcc9`. (The reason for 9 instead of 10 is probably irrelevant, but to make a long story short, I already had gcc9 and didn't want 10 to be installed.) If `sudo port select gcc` doesn't seem to the right thing, try `sudo port install gcc_select` first then repeat.11 What I ended up doing was `sudo port select gcc mp-gcc9`, followed by `sudo port install julia +gcc9`. (The reason for 9 instead of 10 is probably irrelevant, but to make a long story short, I already had gcc9 and didn't want 10 to be installed.) If `sudo port select gcc` doesn't seem to do the right thing, try `sudo port install gcc_select` first then repeat. 12 12 13 13 Furthermore, this is probably an issue for a separate bug report, but if you arrive here after googling the linker error message as I did, you're going to need this bit of advice. There is [https://github.com/macports/macports-ports/pull/4825/files#diff-e13d459d0f7db53fba55e915fb2639b81e77765be3f135b02459c59f27af992dR70 a place in the Portfile] where there's a symlink created to the Fortran compiler in `${workpath}/bin`. If you needed to repeat `port install julia`, say, because you had to `port select` the correct `gcc` first, it will bomb on that `ln` command the second time around.