MacPorts 2.7.0-beta2 now available for testing

Source code and pkgs for MacPorts 2.7.0-beta2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

Help with legacy-support

Greetings. I have been experimenting with Rust on older systems. The first problem I have encountered is the missing symbol "__tlv_bootstrap." Apparently, it was first introduced in 10.7 (https://github.com/rust-lang/rust/issues/10842). Does anyone happen to know if this a candidate for inclusion

Re: GitHub discussions

On Apr 30, 2021, at 14:08, Mark Anderson wrote: > For some of our more long running discussions should we try and leverage > GitHub’s discussion feature? I know that for instance the past Perl > discussion and the Binary only discussion can be hard to wade through on the > list. Might be a good

Re: GitHub discussions

> On May 1, 2021, at 4:23 PM, Ryan Schmidt wrote: > > On Apr 30, 2021, at 14:08, Mark Anderson wrote: > >> For some of our more long running discussions should we try and leverage >> GitHub’s discussion feature? I know that for instance the past Perl >> discussion and the Binary only discus

Re: GitHub discussions

On May 1, 2021, at 17:46, Gregory Anders wrote: > One potential solution might be something like public-inbox.org [1]. This > would provide an easy-to-access archive without fragmenting discussion > further. Why would an archive created with public inbox be easier to use than the archives w

Re: GitHub discussions

I agree with Ryan. Centralization on a less than optimal system is better than fragmenting the communication on "cool systems". My way of finding things in the list: using Google with the modifier `site: lists.macports.org`. (I guess I'm not the only one) On Sun, May 2, 2021 at 12:57 AM Ryan Schm

Re: GitHub discussions

> On May 1, 2021, at 4:57 PM, Ryan Schmidt wrote: > >  > >> On May 1, 2021, at 17:46, Gregory Anders wrote: >> >> One potential solution might be something like public-inbox.org [1]. This >> would provide an easy-to-access archive without fragmenting discussion >> further. > > Why would a

Re: Help with legacy-support

thread_local storage on MacOS is handled by dyld and uses and Apple-specific implementation that came into being in 10.7. The thread_local infrastructure uses symbols that start with “_tlv_*”. See here for details: https://github.com/apple-opensource/dyld/blob/b6b86eb2db14440d373f6f7fd21be4a2bc

Re: Help with legacy-support

should say: On <= 10.6 I have implemented the “emulated_tls” infrastructure that systems without OS implemented TLS use.

Re: Help with legacy-support

I feel like I should have explained this better. Apple’s thread local implementation is in here, and uses their tlv names for these variables. https://github.com/apple-opensource/dyld/blob/b6b86eb2db14440d373f6f7fd21be4a2bc0da897/src/threadLocalVariables.c