libc++ & compiling C++ sources on 10.6 for non-macports users
Mojca Miklavec
mojca at macports.org
Fri Apr 4 23:19:59 UTC 2025
On Sat, 5 Apr 2025 at 00:33, grey wrote:
>
> I'm not too sure since you didn't specify how legacy for older OS X
> systems you are intending?
I did say that it would be ideal if it worked out of the box for
10.7+, though the real answer is "as far back as reasonably
achievable".
(I'm fine with leaving the functionality on 10.6 just for brave users.
Also: I have 10.6 running on an ancient piece of hardware that does,
or at least did the job until now. I suspect that I would not be able
to install 10.7 there, and the other Mac Mini I have is M1, so I'm not
sure if I can easily install an x86_64 10.7 VM there either. Compiling
on 10.6 is most straightforward for me mostly because I have hardware
on a shelf that has been diligently running for years, and switching
to another OS version requires extra hardware resources + extra time
to set it all up.)
> Since MacPorts deprecated Tiger and we lost kencu earlier this year;
> maybe this blog post from Dr. Brian Robert Callahan will be helpful?
>
> https://briancallahan.net/blog/20250329.html
I don't care about Tiger, but having lost Ken really hurt.
This one is going through the hurdles of enabling GCC on an ancient OS
(Tiger), with lots of effort, and resulting in linking against very
exotic stdlibc++. It looks like a lot more work than should be needed,
with probably worse results.
Mojca
More information about the macports-dev
mailing list