Christopher Nielsen

> > @mascguy In principle, we want to place all those `libxc` versions into /libexec and then modify .pc files (or whatever they install) accordingly? > > Yep, exactly! Well,...

FYI, it looks like upstream is up to version 6. (6.1.0 presently.) So you might want to either create another segregated port for that too, following the same pattern you...

> @mascguy CI fail, as before, on `libxc4`, which is as such unrelated to this PR. Well, now you can drop your commits for `libxc` and `libxc4`, as your new...

One more old PR merged, let's keep the momentum going Sergey!

> UPD2. Nop, `libxc5` is still doing something wrong: > > ``` > Could not open /opt/local/lib/libxc.9.dylib: Error opening or reading file (referenced from /opt/local/libexec/libxc5/bin/xc-info) > ``` > > Will...

> @essandess shall this PR also be rebased? :) Just rebased against master, after merging #16149. Let's see how things look, now that Bazel is fixed.

``` 2023-05-03T21:23:53.3244360Z ERROR: py310-tensorflow/work/tensorflow-2.12.0/tensorflow/compiler/xla/pjrt/BUILD:469:11: in cc_library rule //tensorflow/compiler/xla/pjrt:pjrt_future: target '@tf_runtime//:support' is not visible from target '//tensorflow/compiler/xla/pjrt:pjrt_future'. Check the visibility declaration of the former target if you think the dependency is...

> Because I've a bit motivated to delivery https://github.com/macports/macports-ports/pull/18388 which is blocked by this PR, I'd like to suggest a fix: https://github.com/catap/macports-ports/commit/3e43d532198fc89911bdf992af3d0451d5b68e95 which should oversteps the current issue. Awesome! If...

> @mascguy the whole build requires something like 7 hours. We have 3 subports => ~21 hours. See: https://github.com/tensorflow/io/issues/1236 > > I may add a trick from https://github.com/tensorflow/io/pull/1294 which should...

> Long story short: I have no idea how to build it in CI time. > > Using prebuild artifacts won't work because we're building it to be installed under...