[mpich-discuss] MPICH build errors, cannot find -levent(_pthreads)
zhouh at anl.gov
Tue Mar 17 11:07:18 CDT 2020
* >> 14144 /usr/bin/ld: cannot find -levent
* >> 14145 /usr/bin/ld: cannot find -levent_pthreads
Try find where is `libevent` installed and add it to `LIBRARY_PATH`. I think this dependency is pulled in from libtool library, probably one of the ucx dependency. Usually the libtool package should contain the `-L…` for the library. But the breakage will happen if one installs the library to a different paths than the one specified during configure.
These (libtool) magic are wonderful when it works, but so annoyingly difficult to address when it doesn’t 😊
From: Sajid Ali via discuss <discuss at mpich.org>
Reply-To: "discuss at mpich.org" <discuss at mpich.org>
Date: Tuesday, March 17, 2020 at 10:50 AM
To: "discuss at mpich.org" <discuss at mpich.org>
Cc: "Syed, Sajid Ali" <sajidsyed2021 at u.northwestern.edu>
Subject: [mpich-discuss] MPICH build errors, cannot find -levent(_pthreads)
I’m seeing a build error for mpich-3.3.2 on a cluster using gcc-9.3.0. I tried installing mpich using spack while linking against ucx and pmix installed by sysadmins at /usr/local. The error is as follows :
>> 14144 /usr/bin/ld: cannot find -levent
>> 14145 /usr/bin/ld: cannot find -levent_pthreads
>> 14146 collect2: error: ld returned 1 exit status
>> 14147 make: *** [lib/libmpi.la<http://libmpi.la>] Error 1
14148 make: Leaving directory `/tmp/sas4990/spack-stage/spack-stage-
>> 14149 make: *** [all-recursive] Error 1
14150 make: Leaving directory `/tmp/sas4990/spack-stage/spack-stage-
>> 14151 make: *** [all] Error 2
I’m attaching all the spack logs (build-env, build-out and config-args). Let me know if there is any log file that I can send to help debug the issue.
Thanks in advance for the help and hope everyone is staying safe from the virus!
PS: I sent this email with config.log before but it didn't go through, hence I'm sending it again without it. Please feel free to delete/reject the first one.
Sajid Ali | PhD Candidate
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss