-
-
Notifications
You must be signed in to change notification settings - Fork 25
Build issues #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@ChrisRackauckas I just built it via the conda-forge and it seems to work, so shall we close this issue? |
Let me give it another go. |
Well, that's fixed but now on this computer I get: [0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[0]PETSC ERROR: to get more information on the crash.
application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=59
:
system msg for write_line failure : Bad file descriptor when doing using FEniCS
using PyCall
@pyimport fenics
test_triangle = UnitTriangleMesh() Guess I'll keep abusing Travis as my computer haha. |
from dolfin import *
mesh = UnitTriangleMesh() that works from Python. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
conda-forge/fenics-feedstock#46 (comment)
The text was updated successfully, but these errors were encountered: