Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 3:56 PM, Ryan Schmidt wrote: > I wouldn't recommend anyone begin writing any code until it is discussed how > the feature should work. That should avoid spending time writing code that > won't work. sure, if someone were working on a feature it would be reasonable for them

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 14:08, Daniel J. Luke wrote: > On May 24, 2022, at 12:07 PM, Ryan Schmidt wrote: >> I'm not convinced that I would be happy to see such a feature. Just a >> moment's consideration shows how many different parts of MacPorts would need >> modifications to support it, not only

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 12:07 PM, Ryan Schmidt wrote: > I'm not convinced that I would be happy to see such a feature. Just a > moment's consideration shows how many different parts of MacPorts would need > modifications to support it, not only in base but also in the buildbot and in > the package

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: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 09:35, Daniel J. Luke wrote: > - MacPorts could grow a feature by which a port could specify that it needs > to get rebuilt if something it depends on gets rebuilt (this would probably > require another identifier along with epoch-version-revision or would require > some

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

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 23, 2022, at 4:59 PM, Steven Smith wrote: >> What has changed between the time that the buildbot built the package and >> the time that the user installs it? > > The certs in curl-ca-bundle are updated regularly to clear out expired certs. Does the existence of expired certs cause

Reason for rpath usage on arm64

Does anyone know why things seem to be using rpath on arm64 builds? For example: https://trac.macports.org/ticket/64204 The de-facto standard for things installed with MacPorts has been not to use rpath, since MacPorts predates the existence of rpath, and since things have worked fine without