BTW, did you ever run into trouble with libstdc++'s "new ABI"
(https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html) ?
R.
sorry, clang-11-bootstrap
> On Mar 23, 2024, at 00:01, Ken Cunningham
> wrote:
>
> the clang-10-bootstrap port builds against libstdc++ now.
>
> K
the clang-10-bootstrap port builds against libstdc++ now.
K
On Sunday March 17 2024 03:44:00 Sergey Fedorov wrote:
>> but if libc++ 5 was maybe still a bit faster overall than libstc++ the
>situation is now rather reversed though differences remain small
I take that back, the differences aren't always small!
I realised that the so-called "native"
> On Mar 13, 2024, at 4:07 AM, René J.V. Bertin wrote:
>
>> Building against libstdc++ is broken for Intel
>
> Not from what I can tell; I test built an OLD libxmlxx copy against libstdc++
> from GCC13 and that works.
What I rather meant is that Macports cannot handle that properly, since
On Wednesday March 13 2024 03:44:17 Sergio Had wrote:
>Which OS are we talking about?
10.9.5 but that what matters here is that it's a libc++-based OS version.
>Building against libstdc++ is broken for Intel
Not from what I can tell; I test built an OLD libxmlxx copy against libstdc++
from
Which OS are we talking about?
Building against libstdc++ is broken for Intel and arm64, I believe, though it
should be fixable. But the problem is not passing the flag, but broken Apple
headers, it seems.
I managed to build some ports like CMake and a few others against libstdc++ on
Sonoma
Hi,
I've been tinkering a bit with a personal GCC12 build patched to use libc++ by
default, and now find myself unable to build against libstdc++.
`configure.cxxflags-append -stdlib=libstdc++` appears to be filtered out
somewhere in the "base" bowels, and `configure.cxx_stdlib libstdc++`
