Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
Lustre 2.16.0
-
None
-
3
-
9223372036854775807
Description
Looks like when you do --disable-shared configure option, it breaks lutf because lutf expects certain shared libraries to be available.
As I was exploring this it seems the declared functionality of disabling shared libraries per module does not work, you can't disable it for just Lustre or just lnet and so on which makes it even less useful.
In light of the desire to have lutf be the first class citizen, having a configure option that completely breaks it without disabling LUTF seems undesirable. As such we probably need to do the following:
- --disable-shared should disable lutf (or if we can have submodules and only some of them break lutf then just for those submodules)
- Having ability to mix shared libraries + statically built binaries which is the main reason behind disabling shared libraries today in practice, as the libtool shims that create shell scripts instead of binaries and then relink them at every invocation are wasteful and don't work in read-only environments. (getting rid of the libtool cruft would be an ok alternative here I guess?)