In the latest lam-mpi-7.1.1-r3 ebuild, there is an "--enable-shared" switch, but this does not automatically disable the compilation and installation of the standard static library versions. At the moment, both the ".so" and the larger (and as I believe unnecessary) static ".a" library versions are built. In the install docs, it is mentioned that an additional "--disable-static" switch is required. A patch (I mad a simple diff) for the lam-mpi-7.1.1-r3.ebuild to the new -r4 is below. After I used this new -r4 in my portage overlay, the static libraries were not built and of course not installed, which reduced the space usage of the LAM MPI installation. Reproducible: Always Steps to Reproduce: Patch from 7.1.1-r3 to new -r4: 71a72 > --disable-static \
Note: As mentioned in the install docs, compiling both shared and static versions requires double the compilation time. So I guess it's a good improvement to do just half the work :-)
With lam-mpi, static libraries are the default (and indeed, we had to patch in production many shared libs -- see bug #88110). Many MPI-using applications will expect to find the static libs. If any libs are unnecessary outside of 64-bit machines, the shared ones would be. If you have a reason this should still be done, please reopen.
