Installing official Salome Meca 2022 on Windows 10/11 using WSL2 (old approach)

lIlIl

lIlIl To answer my own question: you can use the --fakeroot Singularity option.

$ singularity run --fakeroot ~/sm22/salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif shell
Converting SIF file to temporary sandbox...
Singularity> whoami
root
Singularity> groups
root
Singularity> id
uid=0(root) gid=0(root) groupes=0(root)

k_zurawski

Could you explain briefly how --fakeroot works? Will I be able to change some python files inside the image and will the change be permanent?

lIlIl

It seems that all changes are temporary. It only simulates root privileges, it doesn't actually modify the underlying file system. This is part of what makes Singularity safer than Docker images.
https://docs.sylabs.io/guides/latest/user-guide/fakeroot.html

k_zurawski

lIlIl I was afraid of that because of the sandbox word in your post

lIlIl

Does anyone know where mfront is stored? I would like to call mfront --obuild but I can't find it.
I used find in the root of the WSL distribution and it outputs:

./home/user/dev/codeaster/src/mfront
./home/user/dev/codeaster/src/build/mpi/release/mfront
./opt/public/20221225/gcc8-openblas-ompi2/.installed/mfront
./opt/public/20221225/gcc8-openblas-seq/.installed/mfront

But none of them are executable.

mf

lIlIl

Hello,
within the container in the '/opt/salome_meca/' folder do a 'find . -type f -executable | grep mfront' which will give you all executable files with mfront in the name.
In my case I get:

./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/bin/mfront-3.4.0
./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/bin/mfront-doc-3.4.0
./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/bin/mfront-query-3.4.0
./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/lib/python3.6/site-packages/mfront_3_4_0/init.py
./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/lib/python3.6/site-packages/mfront_3_4_0/mtest/init.py
./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/lib/python3.6/site-packages/mfront_3_4_0/umatxx/Behaviour.py
./V2022.1.0_scibian_univ/prerequisites/Mfront-TFEL340/lib/python3.6/site-packages/mfront_3_4_0/umatxx/init.py
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/bin/mfront-3.4.3
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/bin/mfront-doc-3.4.3
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/bin/mfront-query-3.4.3
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/lib/python3.6/site-packages/mfront_3_4_3/init.py
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/lib/python3.6/site-packages/mfront_3_4_3/mtest/init.py
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/lib/python3.6/site-packages/mfront_3_4_3/umatxx/Behaviour.py
./V2022.1.0_scibian_univ/prerequisites/Mfront_testing-TFEL343/lib/python3.6/site-packages/mfront_3_4_3/umatxx/init.py

So, it should be one of these, I think.

Mario.

lIlIl

mf Thank you! I was able to locate mine. However, I run into errors...

Singularity> ./mfront-3.4.0
./mfront-3.4.0: error while loading shared libraries: libTFELMFront-3.4.0.so.3.4.0: cannot open shared object file: No such file or directory
Singularity> ./mfront-4.1.0
./mfront-4.1.0: error while loading shared libraries: libTFELMFront-4.1.0.so.4.1.0: cannot open shared object file: No such file or directory

I'm stumped.

« Previous Page