-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Source build -- nvcc error : 'cicc' died due to signal 9 (Kill signal) #8018
Comments
Try reducing the amount of parallelism in your build by specifying |
That was the case indeed, thanks @jrhemstad Now it almost compiles, but at the end the following error is thrown:
Does this indicate wrong boost or gcc dependencies? I'm using
|
That kind of looks like wrong boost dependencies. Note that if you wait a bit, we're actually in the process of removing this dependency: #7932 |
For our conda / CI builds we use boost 1.72.0: https://github.com/rapidsai/cudf/blob/branch-0.20/conda/recipes/libcudf/meta.yaml#L42 |
@kkraus14 thanks, using boost 1.72 solved the issue! @jrhemstad that will be in version 0.20, right? I will give this rebuild a try with 0.19 now |
Yep. |
Describe the bug
Compiling cudf from source branch v0.18.1 triggers the following nvcc errors and hangs up the machine where I executed the compilation:
Steps/Code to reproduce bug
The following script in a CentOS 7 docker image with a pre-installed CUDA toolkit triggers the error:
Expected behavior
The build to finish successfully without hang ups and errors
Environment overview (please complete the following information)
docker pull
&docker run
commands usedEnvironment details
Click here to see environment details
The text was updated successfully, but these errors were encountered: