Ticket 6583 - Build failure ./configure --with-pmix without providing a path
Summary: Build failure ./configure --with-pmix without providing a path
Status: RESOLVED DUPLICATE of ticket 10291
Alias: None
Product: Slurm
Classification: Unclassified
Component: Configuration (show other tickets)
Version: 19.05.x
Hardware: Linux Linux
: C - Contributions
Assignee: Tim Wickberg
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2019-02-26 05:17 MST by dani
Modified: 2021-04-30 08:42 MDT (History)
3 users (show)

See Also:
Site: -Other-
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
patch file to fix generation of configure (926 bytes, patch)
2019-02-26 05:17 MST, dani 		Details | Diff
Patch the configure file directly (823 bytes, patch)
2019-02-26 05:23 MST, dani 		Details | Diff
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description dani 2019-02-26 05:17:30 MST 
Created attachment 9312 [details]
patch file to fix generation of configure

Trying to ./configure --with-pmix  without providing a path fails due to a bug in configure - the _x_ac_pmix_dirs is set to yes, overriding the default /usr search path.

Attached a simple patch to fix the m4 file used to create configure.
Basically the patch will result in configure having line 21112 

withval=$with_pmix; if test "x$with_pmix" != xno && "x$with_pmix" != xyes; then :
Comment 1 dani 2019-02-26 05:23:01 MST 
Created attachment 9313 [details]
Patch the configure file directly
Comment 2 dani 2019-02-27 01:54:32 MST 
This issue affects creating RPMs - rpmbuild --with pmix fails due to the yes issue overriding the default dirs, and rpmbuild --with pmix=/path/ or --with pmix /path/ fails due to specfile not accepting arguments for '--with pmix' invocation. The patch only addresses the 1st issue (i.e. no path argument given on command line). I think this issue also affects --with hdf5 and other path parameters.
Comment 3 Tim Wickberg 2019-02-27 22:54:35 MST 
I can see where you're heading, but I think a bit more work is going to be needed on this macro.

If --with-pmix=yes is explicitly set, or a set of directories is given, then configure should fail if it can't find a usable PMIx installation.

Are you interested in tackling that as part of a more extensive patch here?

- Tim

(Thanks for splitting the configure change itself, but I don't need those, and they'll get generated before we check anything in.)
Comment 4 dani 2019-03-03 02:41:35 MST 
I'll try to tackle this as well, but as stated - this affects all '--with-* path' arguments, not just pmix.
Comment 5 Stijn De Weirdt 2019-08-15 07:24:32 MDT 
ran into this too: most other places (eg freeipmi) just keep the default directories to look into, so the search path with --with-mpix becomes the dirs "yes", "/usr", ...
see eg https://github.com/itkovian/slurm/pull/2/commits/b3100796004677d16d8a365afe7dce5a4092c11a
Comment 6 Felip Moll 2021-04-30 08:42:39 MDT 
Hi,

This issue has been fixed in our internal bug 10291.

Thanks for your interest and report.

*** This ticket has been marked as a duplicate of ticket 10291 ***