libc++ & compiling C++ sources on 10.6 for non-macports users

[Sergey Fedorov]

On Sat, Apr 5, 2025 at 7:32 AM Mojca Miklavec <mojca at macports.org> wrote:

> On Sat, 5 Apr 2025 at 00:55, Sergey Fedorov wrote:
> >
> > If you do not have to build texlive often and have some space on a
> drive, won’t it be easier to just use a native C++ runtime, libstdc++, for
> 10.6?
>
> The dependencies require C++17 by now, so gcc 4.2 is not really an option.
>

I did not mean gcc-4.2, that cannot work, of course. gcc14 does work
perfectly fine and supports C++23.
It was a questionable choice of MacPorts to go against macOS default and
force libc++ onto all systems, that just results in more dependencies and
problems like this. By design libstdc++ was the default runtime until 10.9,
I think.

But anyway, in your case it sounds like an unnecessary effort to go out of
the way just for 10.6.


> > On the other hand, you may try using a set-up which I used on powerpc to
> build against libc++. Since it works on 10.6 ppc, there are no reasons for
> it not to work on 10.7+ on Intel. However, that gonna require a custom
> set-up, obviously.
>
> I don't know what setup you have, but libc++ and powerpc sounds like a
> nightmare to set up. (I don't know what is required. When the
> requirements switched to C++11 many years ago, I decided to simply
> drop support for PPC and i386 as that required too much effort to keep
> it working.)
>

I did not mean to build anything for powerpc, of course, since that was not
in the question. MacPorts uses a terribly outdated libc++; what I meant is
to update that, since at least the one from llvm-7 works on 10.6.
On a side note, it is sad that you dropped support for ppc. But without
decent native hardware building anything would be a pain.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20250405/6505ada0/attachment.htm>