-
Notifications
You must be signed in to change notification settings - Fork 32
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
CUDA link issue with incremental build #852
Comments
Hi @esseivaju, I'm not able to reproduce this with the default preset build using the current tip of develop (b427fde) and a local spack env with gcc 11.3 as:
Which commit are you building, and which CUDA version (I'm on 11.7.1)? |
I am building b427fde with gcc11.3 / cuda 12.1. Setting |
I also see similar problem in an updated build. Let me investigate. |
|
I.e. for each compilation of a RDC object file, it generates a 'unique' identifier and thus requires the running of the The symbols:
|
And indeed reverting #847 (completely for now) solves the problem (and of course doing |
OK, maybe we need to just set |
That's odd. It works for me (with and without the space after the |
I see it in the source (and even I see that line executed) but I don't see it in the |
It's not being set as a cache variable, just as a directory scope one (so it will be "seen" by the targets but not saved from one configuration to the next). |
Ok. It is still 'uneffective' (it leads to the proper rebuilds ... I am checking why) |
And this is because there is a (hard) dependency from the result of
|
#848 seems to break incremental builds. Building celeritas from scratch will compile and link everything without issues. Changing a cuda-related file - e.g.
ActionLauncher.device.hh
, even just adding a blank line - then trying to recompile and link will result in the linker error below. This wasn't an issue in 9e1d185.@sethrj @drbenmorgan @pcanal
The text was updated successfully, but these errors were encountered: