You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am surprised that we don't see this problem on NCI. When I install lfric-baf, it copies the tau_psy.f90 files into the infrastructure files, which means this file will be compiled (which then results in linking errors).
Any idea why we don't see this on NCI? I need to manually remove this file from infrastructure/soure/psydata.
Depending on the answer for 1. above, it might be better to move this file out of the infrastructure/source tree, add it to infrastructure/build/psyclone (which doesn't exist here yet, but it is in LFRic core). And then if requested (i.e. tau selected), then grab that file?
The latter approach would also make it easier to support different profiling libs (e.g. Vernier), where atm I am manually copying the psyclone wrapper file into the sources. We could all there wrapper to the psyclone directories, and let fab copy the right file.
The text was updated successfully, but these errors were encountered:
I just realised that on NCI atm we don't trigger any profiling. So no psy_data calls are added to the code, so the fab dependency analysis will never include this file to be compiled.
Still, it would be a better solution if baf grabs up the wrapper files explicitly (depending on command line options).
I am surprised that we don't see this problem on NCI. When I install lfric-baf, it copies the
tau_psy.f90
files into the infrastructure files, which means this file will be compiled (which then results in linking errors).The latter approach would also make it easier to support different profiling libs (e.g. Vernier), where atm I am manually copying the psyclone wrapper file into the sources. We could all there wrapper to the psyclone directories, and let fab copy the right file.
The text was updated successfully, but these errors were encountered: