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

2019-10-25 Thread Mojca Miklavec
On Fri, 25 Oct 2019 at 08:50, Joshua Root wrote: > > It's worth noting that the buildbot will never run into this problem > because it deactivates all installed ports between builds. Thanks a lot for the hint. Simply deactivating a bunch of compilers lead to successful compilation of libxml2.

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

2019-10-25 Thread Joshua Root
On 2019-10-25 16:27 , Mojca Miklavec wrote: > 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

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

2019-10-25 Thread Ken Cunningham
> 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? I have wrestled with this a few times as well. I believe, in the end, I solved it by deactivating clang-5+ (and xar?), and rebuilding libxml2 with

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

2019-10-24 Thread 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

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

2019-10-23 Thread Joshua Root
On 2019-10-24 01:20 , Daniel J. Luke wrote: > On Oct 23, 2019, at 9:58 AM, Ryan Schmidt wrote: >> On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: >>> On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: Or does the port use libxml2? If so, it may be using a bad method of finding libxml2.

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

2019-10-23 Thread Ryan Schmidt
On Oct 23, 2019, at 09:20, Daniel J. Luke wrote: > On Oct 23, 2019, at 9:58 AM, Ryan Schmidt wrote: >> On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: >>> On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: Or does the port use libxml2? If so, it may be using a bad method of finding

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

2019-10-23 Thread Daniel J. Luke
On Oct 23, 2019, at 9:58 AM, Ryan Schmidt wrote: > On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: >> On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: >>> Or does the port use libxml2? If so, it may be using a bad method of >>> finding libxml2. One bad method of finding libxml2 is using the

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

2019-10-23 Thread Ryan Schmidt
On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: > On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: >> Or does the port use libxml2? If so, it may be using a bad method of finding >> libxml2. One bad method of finding libxml2 is using the xml2-config script. > > Should we just patch the

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

2019-10-23 Thread Daniel J. Luke
On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: > Or does the port use libxml2? If so, it may be using a bad method of finding > libxml2. One bad method of finding libxml2 is using the xml2-config script. Should we just patch the xml2-config we distribute (and attempt to push those changes

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

2019-10-22 Thread Ryan Schmidt
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