![]() The meaning of march/mtune on ARM64 is not the same as for x86 architectures ( ). ![]() Particularly for ARM64 I am still trying to understand the march/mtune flags. ![]() I’d like to mention that we’re building both the x86-64 and ARM64 images with the absolute baseline optimisations at the moment (i.e. & make -j8 shared gmsh & make install/fast & cd. Git clone & cd gmsh & mkdir build & cd build & cmake -DCMAKE_BUILD_TYPE=Release -DENABLE_BUILD_SHARED=1 -DENABLE_BUILD_DYNAMIC=1. Git clone & cd mmg & mkdir build & cd build & cmake -DBUILD_SHARED_LIBS=1. apt-get update & apt-get install -y git cmake g++ gfortran python3 python3-numpy python3-scipy python3-pip libpetsc-complex-dev libslepc-complex3.12-dev libopenblas-dev libfltk1.3-dev libfreetype6-dev libgl1-mesa-dev libxi-dev libxmu-dev mesa-common-dev libhdf5-dev libcgns-dev libxft-dev libxinerama-dev libxcursor-dev libxfixes-dev libocct-foundation-dev libocct-data-exchange-dev libocct-ocaf-dev libopenmpi-dev libboost-dev & apt-get clean 4GB + 4GB of swap were enough in my case. Note that to complete this process, a sufficient amount of memory needs to be allocated by docker. Then gmsh can be built from source by running the next three lines. The container need to be launched using the command docker run -ti -name=FEniCSX_real -env PYTHONPATH=/usr/local/dolfinx-real/lib/python3.8/dist-packages:/usr/local/lib -p 8888:8888 dolfinx/lab:latest To recap for anyone looking to run the docker image dolfinx/lab with gmsh:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |