How to handle ports that are still broken because of the icu upgrade

[Mojca Miklavec]

On Wed, 23 Oct 2019 at 03:49, Ryan Schmidt wrote:
>
> icu was recently updated to a new major version. As a result its install_name changed and anything that links with it needs to be rebuilt against the new version.
>
> All ports that declare a dependency on icu already had their revisions increased for this reason. So if you are encountering a port that rev-upgrade identifies as broken due to linking with an older icu, please take a moment to investigate why and perform the correct fix, and don't only increase the revision to rebuild it, which just kicks the can down the road until the next time icu is updated.

I'm not sure if it falls into this category, but the most annoying
problem for me has been clang-9.0 on legacy systems. It depends on
libxml2 which is broken due to icu update, but I cannot rebuild
libxml2 because the compiler is broken. I thought that bootstrapping
was supposed to address this, but apparently it doesn't.

I'm somewhat lost about how even manually address the problem. Should
clang-9.0 use /opt/local/libexec/libcxx-bootstrap/lib/libxml2.2.dylib?

Mojca