wrong version of ncurses about casacore-feedstock HOT 11 CLOSED

Yikes!

It looks like there is a problem because in conda-build 3, the "build environment" installs ncurses version 5, but the "host environment" installs version 6. During the configuration process, cmake decides to link to the host environment's libreadline but somehow decides to pull the dependency on libncursesw from the build environment, getting the wrong version.

This all worked on my machine (and possibly others) because my Linux OS still provides version 5 of libncurses at a system level, so the linking worked out even though the libraries were linking to a non-core library not available in the conda environment.

If I can get cmake to not search the "build environment" for shared library paths, that should fix things. Time to do some digging ...

from casacore-feedstock.

@conda-forge/staged-recipes Tagging since this problem could pop up and cause subtle problems for other cmake-using packages, I think.

from casacore-feedstock.

Ping @conda-forge/core

from casacore-feedstock.

You should be able to rerender the recipe to get the latest ncurses pinning.

from casacore-feedstock.

@scopatz I think the proximate problem here is that the recipe's pinning was newer than that used by some of the build-environment packages; although my local testing is suggesting that the build-env packages have caught up by now. Regardless, I'm pretty sure that nothing about this issue is specific to this particular package beyond its use of cmake, so I worry that comparable hard-to-detect issues will occur in the future.

from casacore-feedstock.

Does this mean we need to be faster getting packages onto the new pinnings?

from casacore-feedstock.

@CJ-Wright That would be nice and would help, I think, but there's always going to be some lag time given how the project operates.

I think I have identified a pretty straightforward way to avoid the problem going forward, though. Testing is ongoing.

from casacore-feedstock.

Ah ok. The bot has some pin-shift-rebuild capabilities but they haven't been put into production yet. I'm trying to gauge need and such so I can do some prioritization.

Attn:
@justcalamari

from casacore-feedstock.

First-cut workaround PR filed.

from casacore-feedstock.

OK @marxide, a build should be coming along that fixes this.

BTW, in the CI output for the build behind the most recent deployed version, conda inspect indeed pointed out the libncurses.5.dylib was "not found" ... it was always a bit weird to me that this was not a build-killing error. But I guess we're moving away from conda inspect anyway, right?

from casacore-feedstock.

Many thanks! Latest build seems to fix this.

from casacore-feedstock.