Re: [mpich-discuss] How to configure mpich without cuda
The “—without-cuda" option causes the compile to fail (where without it the compile succeeds)... [qar@qacentos7 shared]$ make 2>&1 | tee build.txt make all-recursive make[1]: Entering directory `/scr_qacentos7/qar/jenkins/workspace/txliball/n/qacentos7/builds-v/mpich-3.4.1/shared' Making all in src/mpl make[2]: Entering directory `/scr_qacentos7/qar/jenkins/workspace/txliball/n/qacentos7/builds-v/mpich-3.4.1/shared/src/mpl' CCLD libmpl.la ./libtool: line 7472: cd: no/lib: No such file or directory libtool: error: cannot determine absolute directory name of 'no/lib' make[2]: *** [libmpl.la] Error 1 make[2]: Leaving directory `/scr_qacentos7/qar/jenkins/workspace/txliball/n/qacentos7/builds-v/mpich-3.4.1/shared/src/mpl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/scr_qacentos7/qar/jenkins/workspace/txliball/n/qacentos7/builds-v/mpich-3.4.1/shared' make: *** [all] Error 2
On Jul 12, 2021, at 8:24 PM, Zhou, Hui <[email protected]> wrote:
Hi John,
Could you try configure mpich with `--without-cuda`? From: John Cary via discuss <[email protected]> Sent: Monday, July 12, 2021 6:27 PM To: [email protected] <[email protected]>; David Alexander <[email protected]> Cc: John Cary <[email protected]> Subject: [mpich-discuss] How to configure mpich without cuda
Right now it picks up cuda, which links libcuda.so into mpiexec. Is there any way to prevent this?
Thx....John Cary _______________________________________________ discuss mailing list [email protected] <mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss <https://lists.mpich.org/mailman/listinfo/discuss>
participants (1)
-
David Alexander