Thanks,
That seems to do it. I assumed that bash was in MacOS.
-DG
On Dec 22, 2021, at 6:13 AM, Roland Haas rhaas@illinois.edu wrote:
Hello DG,
Since "bash" is the failing program, does typing "bash" (and enter) on the command line work? Did you ever install your own bash? You may also (though I would be surprised) have luck installing "bash" via your package manager. Bash is a fairly basic tool for the system so it not being able to run is odd.
Note: this is likeky more an issue with your system setup / M1 macs in general and less likely to be ET specific so there may be other non-ET users on the Internet reporting it
Yours, Roland
----- Original Message ----- From: "Garrison, David" <Garrison@uhcl.edu mailto:Garrison@uhcl.edu> Sent: 2021-12-22 - 02:07 To: "users@einsteintoolkit.org mailto:users@einsteintoolkit.org" <users@einsteintoolkit.org mailto:users@einsteintoolkit.org> Subject: Re: [Users] Compiling Cactus on M1 Mac
I get the error when I try to compile the code. It is coming from the external library thorns.
Running any thorn-provided configuration scripts...
Running configuration script for thorn FFTW3: Can't exec "bash": Bad CPU type in executable at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 36.
CST error 1: -> Configuration script for thorn FFTW3 failed to start: Bad CPU type in executable
readline() on closed filehandle $lines at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 40.
CST error 2: -> Configuration script for thorn FFTW3 failed to execute: Bad file descriptor (no error message)
Finished running configuration script for thorn FFTW3.
Running configuration script for thorn FORTRAN: Found an ANSI-like Fortran cpp Finished running configuration script for thorn FORTRAN.
Running configuration script for thorn MPI: MPI selected, but MPI_DIR is not set. Computing settings... Found MPI compiler wrapper at /usr/local/bin/mpic++! Installing MPI into /Users/garrison/Applications/Cactus/configs/specgrmhd/scratch/external/MPI MPI was manually configured. Finished running configuration script for thorn MPI.
Running configuration script for thorn OPENBLAS: Can't exec "bash": Bad CPU type in executable at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 36.
CST error 3: -> Configuration script for thorn OPENBLAS failed to start: Bad CPU type in executable
readline() on closed filehandle $lines at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 40.
CST error 4: -> Configuration script for thorn OPENBLAS failed to execute: Bad file descriptor (no error message)
Finished running configuration script for thorn OPENBLAS.
Running configuration script for thorn VECTORS: Can't exec "bash": Bad CPU type in executable at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 36.
CST error 5: -> Configuration script for thorn VECTORS failed to start: Bad CPU type in executable
readline() on closed filehandle $lines at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 40.
CST error 6: -> Configuration script for thorn VECTORS failed to execute: Bad file descriptor (no error message)
Finished running configuration script for thorn VECTORS.
Running configuration script for thorn ZLIB: Can't exec "bash": Bad CPU type in executable at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 36.
CST error 7: -> Configuration script for thorn ZLIB failed to start: Bad CPU type in executable
readline() on closed filehandle $lines at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 40.
CST error 8: -> Configuration script for thorn ZLIB failed to execute: Bad file descriptor (no error message)
Finished running configuration script for thorn ZLIB.
Running configuration script for thorn HDF5: Can't exec "bash": Bad CPU type in executable at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 36.
CST error 9: -> Configuration script for thorn HDF5 failed to start: Bad CPU type in executable
readline() on closed filehandle $lines at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 40.
CST error 10: -> Configuration script for thorn HDF5 failed to execute: Bad file descriptor (no error message)
Finished running configuration script for thorn HDF5.
Running configuration script for thorn LAPACK: Can't exec "bash": Bad CPU type in executable at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 36.
CST error 11: -> Configuration script for thorn LAPACK failed to start: Bad CPU type in executable
readline() on closed filehandle $lines at /Users/garrison/Applications/Cactus/repos/flesh/lib/sbin/ConfigScriptParser.pl line 40.
CST error 12: -> Configuration script for thorn LAPACK failed to execute: Bad file descriptor (no error message)
Finished running configuration script for thorn LAPACK. Checking consistency... Argument "1.0D-5" isn't numeric in addition (+) at /Users/garrison/Applications/Cactus/lib/sbin/CST line 793. Argument "1.0D-5" isn't numeric in addition (+) at /Users/garrison/Applications/Cactus/lib/sbin/CST line 794.
There were 12 errors during execution of the CST These must be corrected before compilation can proceed
Warnings were generated during execution of the CST
CST error 1: -> Configuration script for thorn FFTW3 failed to start: Bad CPU type in executable
CST error 2: -> Configuration script for thorn FFTW3 failed to execute: Bad file descriptor (no error message)
CST error 3: -> Configuration script for thorn OPENBLAS failed to start: Bad CPU type in executable
CST error 4: -> Configuration script for thorn OPENBLAS failed to execute: Bad file descriptor (no error message)
CST error 5: -> Configuration script for thorn VECTORS failed to start: Bad CPU type in executable
CST error 6: -> Configuration script for thorn VECTORS failed to execute: Bad file descriptor (no error message)
CST error 7: -> Configuration script for thorn ZLIB failed to start: Bad CPU type in executable
CST error 8: -> Configuration script for thorn ZLIB failed to execute: Bad file descriptor (no error message)
CST error 9: -> Configuration script for thorn HDF5 failed to start: Bad CPU type in executable
CST error 10: -> Configuration script for thorn HDF5 failed to execute: Bad file descriptor (no error message)
CST error 11: -> Configuration script for thorn LAPACK failed to start: Bad CPU type in executable
CST error 12: -> Configuration script for thorn LAPACK failed to execute: Bad file descriptor (no error message)
On Dec 21, 2021, at 9:59 PM, Roland Haas rhaas@illinois.edu wrote:
Hello DG,
Has anyone had success getting the Einstein Toolkit to compile on a M1 powered Mac? I get "Bad CPU type in executable” when I try.
The newest version (2021_11) may work (if you follow the instructions at the top of the new user tutorial https://urldefense.com/v3/__https://raw.githubusercontent.com/nds-org/jupyte... https://urldefense.com/v3/__https://raw.githubusercontent.com/nds-org/jupyter-et/master/tutorial-server/notebooks/CactusTutorial.ipynb__;!!BCR0FSePrR4x!HSpcf0NgavIu9EHi3H0eOK67623_FGUuCixULyS0-dFv1GlDrNXWFU74OCV7LlXEXKuaelhmNYjW4PokPQ$ to install homebrew or macports and some of the support packages).
Do you get this error when trying to run or while compiling?
Yours, Roland
-- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from https://urldefense.com/v3/__http://keys.gnupg.net__;!!BCR0FSePrR4x!HSpcf0Nga... https://urldefense.com/v3/__http://keys.gnupg.net__;!!BCR0FSePrR4x!HSpcf0NgavIu9EHi3H0eOK67623_FGUuCixULyS0-dFv1GlDrNXWFU74OCV7LlXEXKuaelhmNYhh7H6pKQ$ .
-- David Garrison, Ph.D. Interim Associate Dean for the College of Science and Engineering, Professor and Former Chair of Physics University of Houston-Clear Lake Bayou 3611 Houston, TX 77058
Tel: 281-283-3796 Fax: 281-283-3709 http://sce.uhcl.edu/garrison http://sce.uhcl.edu/garrison http://www.uhcl.edu/physics http://www.uhcl.edu/physics
"If we knew what it was we were doing, it would not be called research, would it?" ‹ Albert Einstein.
Users mailing list Users@einsteintoolkit.org mailto:Users@einsteintoolkit.org https://urldefense.com/v3/__http://lists.einsteintoolkit.org/mailman/listinf... https://urldefense.com/v3/__http://lists.einsteintoolkit.org/mailman/listinfo/users__;!!BCR0FSePrR4x!HSpcf0NgavIu9EHi3H0eOK67623_FGUuCixULyS0-dFv1GlDrNXWFU74OCV7LlXEXKuaelhmNYhtd9GpZg$