Added definitions from header file
Description
Addresses issue #1911
This pull request requires additional validation before any workflows can run on NVIDIA's runners.
Pull request vetters can view their responsibilities here.
Contributors can view more details about this message here.
CLA Assistant Lite bot All Contributors have signed the CLA.
I have read the Contributor License Agreement and I hereby accept the Terms.
/ok to test
Command Bot: Processing...
/ok to test
Command Bot: Processing...
@khalatepradnya this doesn't give and error in other files but this some thing gives an error in qubit_qis.h . Why is this happening ?
@khalatepradnya can you please explain me what's the problem here ?? So I can try to fix this
@khalatepradnya this doesn't give and error in other files but this some thing gives an error in qubit_qis.h . Why is this happening ?
Is this the error message you get when building your branch locally?
(I see that CI is failing with error: 'annotate' attribute requires a string)
@khalatepradnya can you please explain me what's the problem here ?? So I can try to fix this
I don't see any changes to cmake in this PR. I suspect the build is not able to locate the new file, can you check target_include_directories?
@khalatepradnya can you please explain me what's the problem here ?? So I can try to fix this
I don't see any changes to cmake in this PR. I suspect the build is not able to locate the new file, can you check
target_include_directories?
Ok I will try this
@khalatepradnya I didn't find any issues with target_include_directories
@khalatepradnya this doesn't give and error in other files but this some thing gives an error in qubit_qis.h . Why is this happening ?
Is this the error message you get when building your branch locally? (I see that CI is failing with
error: 'annotate' attribute requires a string)
Unfortunately, __attribute__((annotate(thing))) isn't very smart and strictly requires a C style string literal to appear inline for thing. Sad, but true. So we can't use a symbolic for thing in these cases.
@ParamThakkar123 do you want to take another stab at this one?
@ParamThakkar123 do you want to take another stab at this one?
Yeah would like to work on this. But would need some help from your side not to solve this issue but to get a better understanding of this codebase.
@ParamThakkar123 do you want to take another stab at this one?
Yeah would like to work on this. But would need some help from your side not to solve this issue but to get a better understanding of this codebase.
Hi! If you want to continue investigating this build failure, I recommend first aligning with main and re-running the build. If you happen to have error message from your local build environment, please share it so we can debug further. Thanks!
