Yes, the linker in CLT 15.0 is also affected.  I believe it is exactly the
same linker as the one in Xcode 15.0.


On Sat, Oct 7, 2023 at 9:46 AM Jim Secan <james.se...@gmail.com> wrote:

> A related question - I install and use only the CLI toolkit for Xcode, not
> the entire Xcode package.  Does this linker problem also effect use of the
> CLI toolkit, or can I safely upgrade to just the toolkit (I’m still on
> Ventura).
>
> Jim
> Seattle, WA
> > On 10/07/2023, at 8:03 AM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:
> >
> > Hi,
> >
> >> On 7 Oct 2023, at 3:40 pm, Murray Eisenberg <murrayeisenb...@gmail.com>
> wrote:
> >>
> >> 
> >>> OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton <kevi...@kilohotel.com>
> wrote:
> >>>
> >>> I'm pondering whether I should upgrade to macOS Sonoma now, or
> continue to wait.  Generally speaking, how well is Macports working on
> Sonoma?  I have seen a surprising small number of issues posted on this
> list, and am wondering whether that is a good reflection of the status.
> >>
> >>
> >> It depends on which ports you require. Most of those I had under
> Ventura I could finally get installed under Sonoma.
> >>
> >> But a number of ports will not as yet re-install under Sonoma owing to
> a change in C compiler flags in Xcode 15 (and Sonoma seems not to allow
> using an earlier version of Xcode).
> >
> >
> > Not wishing to be pedantic, but the issue is not relating to the
> compiler, but instead the linker. Xcode 15 switched to a new implementation
> which has issues in some scenarios, for instance whenever asked to link
> against object files or dylibs created with GCC. A common reason for this
> is ports that need to use GCC to build fortran source code. OpenBLAS is a
> specific example that a number of ports use and thus are having issues
> linking against.
> >
> > Workarounds exist, basically by using specific linker options to go back
> to using the so called ‘classic’ linker. The problem is not all builds are
> easy to convince to use these flags.
> >
> > Cheers Chris
> >
> >>
> >> Among those troublesome ports is sbcl, and unfortunately the maxima
> port depends on sbcl.
>

Reply via email to