Open
Conversation
cuda 10.1 on ubuntu 18 with gcc 4.9 will fail to build with the following: nvcc fatal : '-D_FORCE_INLINES': expected a number this is caused by the use of -O, adding a number -O0 solves it.
|
it failed for me with the following error: 'O0' is an unknown mex argument Do you know how to fix this? Thank you |
|
To fix 'nvcc fatal : '-DNDEBUG': expected a number' , But I still get an error like : Please give me any advice. |
|
You just need to comment the line 340 (flags.base{end+1} = '-O' ). |
Thank you for your answer, I also meet this question. Is there any defect to comment this line340? Thank you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cuda 10.1 on ubuntu 18 with gcc 4.9 will fail to build with the following:
nvcc fatal : '-D_FORCE_INLINES': expected a number
this is caused by the use of -O, adding a number -O0 solves it.
fix #1212