Opened 8 years ago
Closed 8 years ago
#51882 closed defect (fixed)
dolfin ImportError: No module named _common
Reported by: | sarah_frank@… | Owned by: | seanfarley (Sean Farley) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | ||
Port: | dolfin |
Description
After installing dolfin through macports, I am unable to use it successfully. I get an error after importing:
>>> import dolfin >>> Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/dolfin/__init__.py", line 16, in <module> from . import cpp File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/dolfin/cpp/__init__.py", line 42, in <module> exec("from . import %s" % module_name) File "<string>", line 1, in <module> File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/dolfin/cpp/common.py", line 25, in <module> _common = swig_import_helper() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/dolfin/cpp/common.py", line 24, in swig_import_helper return importlib.import_module('_common') File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) ImportError: No module named _common
It appeared that someone else had similar problems but it looked like they uninstalled and reinstalled macports to fix, but after trying a few different things and then uninstalling and reinstalling macports I am still getting the same error message.
Change History (7)
comment:1 Changed 8 years ago by seanfarley (Sean Farley)
Owner: | changed from macports-tickets@… to sean@… |
---|---|
Status: | new → assigned |
comment:2 Changed 8 years ago by mf2k (Frank Schima)
Keywords: | dolfin importerror removed |
---|
comment:3 follow-up: 4 Changed 8 years ago by seanfarley (Sean Farley)
Updated in r150520. Can you try to update and test?
comment:4 Changed 8 years ago by sarah_frank@…
comment:5 Changed 8 years ago by seanfarley (Sean Farley)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Yay!
comment:6 Changed 8 years ago by sarah_frank@…
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Hello! I just updated my macports because I was having trouble installing py27-slepc4py but in the process there was a problem with rebuilding dolfin. I uninstalled dolfin, ran port upgrade outdated, and now when I try to reinstall dolfin I get the following error:
Error: org.macports.build for port dolfin returned: command execution failed
I don't really understand the log file but I thought this part may be helpful:
:info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolfin-2016.1.0/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolfin-2016.1.0/build" && /usr/bin/make -j4 -w all VERBOSE=ON :info:build Exit code: 2 :error:build org.macports.build for port dolfin returned: command execution failed :debug:build Error code: CHILDSTATUS 19770 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname"
comment:7 Changed 8 years ago by mf2k (Frank Schima)
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
That is an entirely different issue and so you should open a new ticket. Also, without the complete main.log, I don't think sean will be able to help you.
I'm about to push an updated version of dolfin so hopefully that will fix this.