Installation with mac M1

[crpiceda]

Installation with mac M1

[crpiceda]

Got it, I was specifying the prefix with a directory with the same name as the INSTALL file, so they were both conflicting. I got confused with the instructions because the suggested prefix actually has this name. By setting another name for the directory I was able to make the installation. Thank you!

[roystgnr]

Weird. It looks to me like that -bind_at_load is coming from the latest libtool, but we last specifically upgraded our autotools version because the newest tools added M1 support.

But it's a deprecated warning, not (yet) an error, so maybe they're just running a bit behind with that. It sounds like your make completed anyway? You could try a make check to see for sure.

The failing make install is because you've got an install directory set that conflicts with an existing file. Your source tree is at /Users/crpiceda/libmesh/libmesh, which means /Users/crpiceda/libmesh/libmesh/install is (on a case-insensitive filesystem like OSX) conflicting with the instructions file /Users/crpiceda/libmesh/libmesh/INSTALL. Try configuring to use a different install directory.

[crpiceda]

Thank you for the reply.
I run make check and I got these last lines in the terminal

make[4]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/examples/vector_fe/vector_fe_ex5'
make[3]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/examples/vector_fe/vector_fe_ex5'
make[2]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/examples/vector_fe/vector_fe_ex5'
make[2]: Entering directory '/Users/crpiceda/libmesh/libmesh/build/examples'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/examples'
make[1]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/examples'
Making check in doc
make[1]: Entering directory '/Users/crpiceda/libmesh/libmesh/build/doc'
Making check in html
make[2]: Entering directory '/Users/crpiceda/libmesh/libmesh/build/doc/html'
make  check-am
make[3]: Entering directory '/Users/crpiceda/libmesh/libmesh/build/doc/html'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/doc/html'
make[2]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/doc/html'
make[2]: Entering directory '/Users/crpiceda/libmesh/libmesh/build/doc'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/doc'
make[1]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build/doc'
make[1]: Entering directory '/Users/crpiceda/libmesh/libmesh/build'
make[1]: Nothing to be done for 'check-am'.
make[1]: Leaving directory '/Users/crpiceda/libmesh/libmesh/build

so I think the tests passed succesfully.
What should be then the path I should use for the configuration in ../configure --prefix=/Users/crpiceda/libmesh/libmesh/install --disable-metaphysicl?

[roystgnr]

The path is up to you. I set ../configure --prefix=~/LIBRARIES/libmesh-foo (where "foo" is "normal" or "complex" or whatever name I give to a weird configuration I want to be able to test with often), but that's just me. The only real restriction here is that you have to have permission to enter and write to any of the already-existing directories in the path you give and none of those levels can be an already-existing file. If my ~/LIBRARIES directory was chmod u-w or if it was actually a file rather than a directory (as in your case with libmesh/install) then I naturally wouldn't be able to install to a subdirectory of it.

[roystgnr]

Yikes. Which instructions are suggesting that prefix?

[jwpeterson]

Yikes. Which instructions are suggesting that prefix?

We kind of do it in Step 5 of our README instructions:

../configure --prefix=/path/to/libmesh/install

[roystgnr]

Oh, my. That is the most natural interpretation of that isn't it? I'll change it.

[crpiceda]

good to know it was not only my interpretation as beginner :)
Only for the record, I realised I had some conflicts with the default compilers (which were pointing to usr/local/bin), but I fixed it by declaring the compilers installed by homebrew supporting arm64 architecture. I leave my config command in case someone finds it useful in the future:
../configure --prefix=/Users/crpiceda/libmesh/libmesh/installed \ CC=/opt/homebrew/bin/gcc-13 \ CXX=/opt/homebrew/bin/g++-13 \ --disable-metaphysicl