Linking libMacportsLegacySupport privately?

[René J.V. Bertin]

Hi,

I've been experimenting with libc++ 17 which is a prerequisite to using GCC13+ with libc++ instead of libstdc++ . 

I kept the static legacy-support library linking (may have had to, can't remember that) and just now realise that all the functions from that archive (or at least the from the modules that get pulled in) are exported by libc++ . Which means that C++-based function availability checking via autoconf, cmake etc. give false positives on systems where those functions require legacy-support.

Is there a way to link the legacy-support archive privately that doesn't involve a significant overhaul of the build system?

I think this question is of (potential) interest beyond my libc++ experiment.

Thanks,
R.