Re: Reason for rpath usage on arm64

Iain has added what MacPorts needed to the gcc branches he maintains, and plans to push them through. This option will let us add the needed rpath to where MacPorts puts the gcc libraries. --with-darwin-add-path= Also, re cmake PG, changing the cmake option for in-build library paths should

Re: Reason for rpath usage on arm64

On May 30, 2022, at 01:01, Ken Cunningham wrote: > ah yes, your question was arm64-specific so that led to the gcc assumption. > > the way the cmake PG configures cmake breaks testing on all archs and systems. It worked for me on Catalina x86_64 but not on Big Sur arm64, and I was trying to

Re: Reason for rpath usage on arm64

ah yes, your question was arm64-specific so that led to the gcc assumption. the way the cmake PG configures cmake breaks testing on all archs and systems. this comes up regularly, eg https://lists.macports.org/pipermail/macports-dev/2021-September/043754.html Perhaps it might beneficially be

Re: Reason for rpath usage on arm64

On May 24, 2022, at 10:22, Ken Cunningham wrote: > >> Does anyone know why things seem to be using rpath on arm64 builds > > Basically, it comes down to the fact that Apple has disallowed > DYLD_LIBRARY_PATH to work on newer systems. > So gcc is installing it’s libraries with the @rpath

Re: Reason for rpath usage on arm64

On 2022-5-25 03:01 , Ken Cunningham wrote: That comes right from Iain - here's the relevant gcc ticket I believe: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 I'm sure Iain would be delighted to find a way around this. OK, so it's

Re: Reason for rpath usage on arm64

Hi, On Tue, May 24, 2022 at 10:01:09AM -0700, Ken Cunningham wrote: > That comes right from Iain - here's the relevant gcc ticket I believe: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 > > I'm sure Iain would be delighted to find a way around this. MacPorts works around this by

Re: Reason for rpath usage on arm64

> On 24 May 2022, at 4:22 pm, Ken Cunningham > wrote: > >  >> >> Does anyone know why things seem to be using rpath on arm64 builds > > Basically, it comes down to the fact that Apple has disallowed > DYLD_LIBRARY_PATH to work on newer systems. > > gcc for Darwin has one developer

Re: Reason for rpath usage on arm64

Oh, nothing whatsoever to do with arm64 specifically. This is going to affect all gcc builds on all darwin-supported architectures once Iain pushes it through to all the branches he plans to keep supporting. On Tue, May 24, 2022 at 9:50 AM Joshua Root wrote: > On 2022-5-25 01:22 , Ken

Re: Reason for rpath usage on arm64

That comes right from Iain - here's the relevant gcc ticket I believe: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 I'm sure Iain would be delighted to find a way around this. On Tue, May 24, 2022 at 9:50 AM Joshua Root wrote: > On 2022-5-25 01:22 , Ken Cunningham wrote: > >> Does

Re: Reason for rpath usage on arm64

On 2022-5-25 01:22 , Ken Cunningham wrote: Does anyone know why things seem to be using rpath on arm64 builds Basically, it comes down to the fact that Apple has disallowed DYLD_LIBRARY_PATH to work on newer systems. This is the first I've heard of it. Is this supposed to be the case only

Re: Reason for rpath usage on arm64

> Does anyone know why things seem to be using rpath on arm64 builds Basically, it comes down to the fact that Apple has disallowed DYLD_LIBRARY_PATH to work on newer systems. gcc for Darwin has one developer working on it, practically. Iain. He has been maintaining it for 10+ years, wrote the