|
Veronika,
There is something screwy going on with some hombrew gcc installs. Not sure why.
In many case, creating a symbolic link libgcc_s.dylib -> libgcc_s.1.1.dylib in /opt/homebrew/opt/gcc/lib/gcc/11 fixes this
Regards,
Blaise
I pulled the updated repo but now I get a different error also related to architecture:
ld: file not found: @rpath/libgcc_s.1.1.dylib for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: command '/Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/bin/mpicc' failed with exit code 1
**************************ERROR*************************************
Error building petsc4py.
********************************************************************
make[2]: *** [petsc4pybuild] Error 1
**************************ERROR*************************************
Error during compile, check arch-darwin-c-debug/lib/petsc/conf/make.log
********************************************************************
Any idea about this one? Thank you
Hello Satish,
By the repo you mean the main PETSc repository?
Thank you, Veronika
A fix for M1 was recently pushed to the git repo.
Can you try using it [with either release or main branches] - and see if that works?
Satish
On Fri, 8 Apr 2022, Veronika Ulanova wrote:
> Hi,
>
> I have been trying to configure the petsc4py package along with my PETSc
> installation for my research. I have searched for solutions on the internet
> but there was no luck, this is the error I get when I am trying to
> configure PETSC and use it to run examples of code that utilise the
> petsc4py package...
>
>
>
> File
> "/Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/PETSc.py",
> line 3, in <module>
>
> PETSc = ImportPETSc(ARCH)
>
> File
> "/Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/lib/__init__.py",
> line 29, in ImportPETSc
>
> return Import('petsc4py', 'PETSc', path, arch)
>
> File
> "/Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/lib/__init__.py",
> line 73, in Import
>
> module = import_module(pkg, name, path, arch)
>
> File
> "/Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/lib/__init__.py",
> line 58, in import_module
>
> with f: return imp.load_module(fullname, f, fn, info)
>
> File "/opt/homebrew/Cellar/[email protected]/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/imp.py",
> line 242, in load_module
>
> return load_dynamic(name, filename, file)
>
> File "/opt/homebrew/Cellar/[email protected]/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/imp.py",
> line 342, in load_dynamic
>
> return _load(spec)
>
> ImportError:
> dlopen(/Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/lib/arch-darwin-c-debug/
>
PETSc.cpython-39-darwin.so <http://petsc.cpython-39-darwin.so/>, 2): no
> suitable image found. Did find:
>
> /Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/lib/arch-darwin-c-debug/
>
PETSc.cpython-39-darwin.so <http://petsc.cpython-39-darwin.so/>: mach-o,
> but wrong architecture
>
> /Users/veronikaulanova/Documents/documents/Oxford_work/petsc/arch-darwin-c-debug/lib/petsc4py/lib/arch-darwin-c-debug/
>
PETSc.cpython-39-darwin.so <http://petsc.cpython-39-darwin.so/>: stat()
> failed with errno=25
>
>
> As you can see I am using an M1 mac and therefore that causes the petsc4py
> package to give me an error (highlighted above), but do you have any idea
> of how I can solve it or why it is even there? I know that the new M1 has a
> different architecture to intel macs but I have no idea of where to
> start with fixing this or how to make it work. Any help would be much
> appreciated, thank you in advance.
>
> Kind Regards, Veronika
>
--
Professor, Department of Mathematics & Statistics
Hamilton Hall room 409A, McMaster University
1280 Main Street West, Hamilton, Ontario L8S 4K1, Canada
Tel. +1 (905) 525 9140 ext. 27243
|
