-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with slurm 19.05.01 #28
Comments
I can confirm that the slurmdb is merged in with the slurm library. There is a note from Schedmd:
It is under the "28 May 2019" section of the |
I have a compilation issue whereby I encounter the following error:
My configure command is: Libraries and includes are present as stated in the help text:
My Slurm installation is compiled from source using Intel compilers. I am getting the same error when running against Slurm 18.08.8 making me think I am potentially missing a compilation flag in either Slurm or drmaa. @dpryan79 did you install Slurm 19.05.1 from packages or compile from source? |
@ocfmatt if you look in your You can remove the |
@EricR86 Thanks for your quick reply. I removed "-lslurmdb" and was able to configure and make after I downloaded the release source code. I had an uninitialised drmaa_utils path causing other errors. |
Hi all,
What is odd is that it seems to be defined in the headers;
Command used to configure: |
libdrmaa should be linking against libslurm.so, but that doesn't seem to be the case for you, which I think is the cause of the problem. |
Hi @dpryan79 you were right I did a silly mistake I removed the whole line in the configure rather than leaving |
Hi, I also met this problem as natefoo described .and i revised this line in configure like this . #line 14022 SLURM_LIBS="-lslurm" |
At least when I built it just now, slurm 19.05.01 doesn't ship a libslurmdb.so, so the linking test run by configure fails. Removing the linking to it here solves the issue https://github.com/natefoo/slurm-drmaa/blob/master/m4/ax_slurm.m4#L75 but it'd be good if someone else confirmed before this is implemented.
The text was updated successfully, but these errors were encountered: