libfabric: add 2.5.0

[msimberg]

• https://github.com/ofiwg/libfabric/releases/tag/v2.5.0
• https://github.com/ofiwg/libfabric/blob/v2.5.0/NEWS.md#v250-fri-march-20-2026

Also adds a conflict with cxi because of ofiwg/libfabric#12036.

[msimberg]

Ping @darrylabbate (I think you're not in maintainers so I can't explicitly request a review from you).

[msimberg]

@ax3l, @vicentebolea, @williamfgc, @soumagne the adios2 and mercury builds failed with libfabric-related linker errors which I assume really comes from this new version:

• adios2: https://gitlab.spack.io/spack/spack-packages/-/jobs/21128168
• mercury: https://gitlab.spack.io/spack/spack-packages/-/jobs/21128170

In the latest commit I tried to add generic conflicts with the latest libfabric version (still waiting for CI to see if that's sufficient (edit: the conflicts seem to have helped in the sense that nothing is rebuilt now)) but perhaps you want to have a look if more specific constraints are required?

[soumagne]

hmm that's odd. I think what this indicates is that somehow an older libfabric version is picked up at link time, ie. it is correctly compiling against libfabric 2.5.0 but then maybe another library is pulling an older libfabric ? this is usually what would cause the errors of the type undefined reference to fi_freeinfo@FABRIC_1.9' where FABRIC_1.9 symbols are only defined in the newer version of libfabric.

[msimberg]

I've added a conflict for this issue with the cxi provider: ofiwg/libfabric#12036.

hmm that's odd. I think what this indicates is that somehow an older libfabric version is picked up at link time, ie. it is correctly compiling against libfabric 2.5.0 but then maybe another library is pulling an older libfabric ? this is usually what would cause the errors of the type undefined reference to fi_freeinfo@FABRIC_1.9' where FABRIC_1.9 symbols are only defined in the newer version of libfabric.

Yeah, it is strange indeed. I unfortunately don't have any insight into the runners if there might actually be another libfabric installed somewhere on that runner/in that environment. Would you be ok with keeping the conflict for now or would that block you in reasonable use cases? @alalazo or @haampie would you have more information on the runner tha failed (or know who else to ask)?

[soumagne]

I've added a conflict for this issue with the cxi provider: ofiwg/libfabric#12036.

hmm that's odd. I think what this indicates is that somehow an older libfabric version is picked up at link time, ie. it is correctly compiling against libfabric 2.5.0 but then maybe another library is pulling an older libfabric ? this is usually what would cause the errors of the type undefined reference to fi_freeinfo@FABRIC_1.9' where FABRIC_1.9 symbols are only defined in the newer version of libfabric.

Yeah, it is strange indeed. I unfortunately don't have any insight into the runners if there might actually be another libfabric installed somewhere on that runner/in that environment. Would you be ok with keeping the conflict for now or would that block you in reasonable use cases? @alalazo or @haampie would you have more information on the runner tha failed (or know who else to ask)?

Yeah I don't think you should add that conflict and we'll need to remove it anyway but that's a good experiment.