Thanks for the information, interesting. These paths are auto generated during setup and installation as far as i know, so either we're breaking something in the build process within the package or as you point out it's an issue with the package building system. I'll look into it once i have a bit more time.
Since I'm barely keeping this package updated I'd suggest that you use the upstream Lmod project source with the dependencies that come with this package, you'll get more bug fixes, Performance and features out of it in a production environment. That's what we used to do on live HPC systems since a lot of software needs to be built by hand outside of the distro packaging anyway. Thanks, Aaron On Mon 17. Feb 2020 at 19:45, Tamar Klein <[email protected]> wrote: > I did try with "apt source lmod" on the same system, in order to check you > suggestion. > So yes, it is the same version as debian's package, we're currently using > the packages from: > http://snapshot.debian.org/archive/debian/20200217T030244Z/ > > (We started upgrading the system this morning, so the date of the archive > is this morning's) > > > On Mon, Feb 17, 2020 at 8:40 PM Aaron Zauner <[email protected]> wrote: > >> It might be related to the version. Keep in mind that the version >> packaged for Debian is quite old. Did you try with the same version? >> >> On Mon 17. Feb 2020 at 19:39, Tamar Klein <[email protected]> wrote: >> >>> Hi >>> >>> Thanks for your suggestion. >>> >>> When downloading the source package and building it locally, the paths >>> seems to be correct. >>> So I guess that the problem is either debian packagers used the same >>> version for powerpc and x86 or was doing cross-site compilation without >>> passing the correct parameters. >>> It seems that the package is only have to be re-built in powerpc >>> environment. >>> >>
