Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CUB bundle missing in GitHub's tarball

See original GitHub issue

I am trying to build a conda package for v8.0.0rc1 locally, and notice that cupy/core/include/cupy/cub/ is empty in https://github.com/cupy/cupy/archive/v8.0.0rc1.tar.gz. So, attempting to build CuPy would get this error message (that we deliberately set up):

        The folder cupy/core/include/cupy/cub/ is a git submodule but is
        currently empty. Please use the command

            git submodule update --init

        to populate the folder before building from source.

The current workaround I have is to download and move CUB 1.8.0 to the include path, but I don’t think this is expected behavior.

Issue Analytics

State:
Created 3 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

2reactions

leofangcommented, Aug 28, 2020

I think so, although it’s probably not a big deal. We can inject a file containing the CUB version string to cupy_package_data (added in #3879) and instruct setup.py to look it up during build time.

2reactions

kmaehashicommented, Aug 28, 2020

The GitHub tarball is auto-generated by Github from the git tag, so we can’t do anything. (Maybe we can improve the message if cupy/core/include/cupy/cub/.git is absent, though)