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 was investigating whether --install-prefix= was a better option to use for build than --destination= when building using the Spack recipe for charmplusplus 7 and 8.
This is a build outside Spack, just using an openmpi, ucx and pmix built by it (hence the long --basedir placeholder paths).
This builds and installs successfully both inside and outside Spack, but I cannot then build namd using it because include/conv-mach-opt.sh tries to source include/cc-gcc.sh, include/conv-mach-ompipmix.sh and include/conv-mach-smp.sh all from the original source location, which would be deleted after the install. Those files all exist in the install, they just aren't being referenced in that location.
include/completion.def.h and include/CkIO_impl.def.h are the only other non-binaries that also mention the source location, but those appear to all be comment lines.
The text was updated successfully, but these errors were encountered:
I was investigating whether
--install-prefix=
was a better option to use forbuild
than--destination=
when building using the Spack recipe for charmplusplus 7 and 8.This is a build outside Spack, just using an openmpi, ucx and pmix built by it (hence the long
--basedir
placeholder paths).This is using the 8.0.0 release tarball.
This builds and installs successfully both inside and outside Spack, but I cannot then build namd using it because
include/conv-mach-opt.sh
tries to sourceinclude/cc-gcc.sh
,include/conv-mach-ompipmix.sh
andinclude/conv-mach-smp.sh
all from the original source location, which would be deleted after the install. Those files all exist in the install, they just aren't being referenced in that location.include/completion.def.h
andinclude/CkIO_impl.def.h
are the only other non-binaries that also mention the source location, but those appear to all be comment lines.The text was updated successfully, but these errors were encountered: