python-meep team mailing list archive
-
python-meep team
-
Mailing list archive
-
Message #00026
Re: Build Problems
Hello Andrea,
I was on vacation with no access to e-mail, so apologies for the late
reply... and our community of mailinglist subscribers is still small.
Maybe somebody else already replied to you directly?
* please check if you have installed all the required prerequisites as
specified in the README file, specifically check if you installed
numpy/scipy and the Python 2.6 development headers/libs:
sudo apt-get install python-scipy
sudo apt-get install python-dev
Do a new "locate npy_common.h" after that: it should now find the file
in a subdirectory of /usr/lib. Is that the case?
If you still get the same error, then use the -I directives to specify
the directory where it can find the header files
for example :
./make -I/usr/lib/python2.6/dist-packages/numpy/core/include
I look forward to your feedback.
wbr
Emmanuel
On Mon, 2010-07-26 at 14:37 +0200, Andrea Armaroli wrote:
> Dear Python-meep developers,
>
> I use ubuntu 9.04 and I can't build python-meep.
>
> Is there someone who could please help me?
>
>
> I attach the make result
>
> Directories for SWIG -I option : ['/usr/include']
> Directories for -L option : ['/usr/lib']
> running clean
> removing 'build/temp.linux-x86_64-2.6' (and everything under
> it)
> removing 'build/lib.linux-x86_64-2.6' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.6' does not exist -- can't clean it
> removing 'build'
> Directories for SWIG -I option : ['/usr/include']
> Directories for -L option : ['/usr/lib']
> running build_ext
> building '_meep' extension
> swigging meep.i to meep_wrap.cpp
> swig -python -c++ -w503,389,302,362,314,509,451 -I/usr/include
> -o meep_wrap.cpp meep.i
> creating build
> creating build/temp.linux-x86_64-2.6
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2
> -Wall -Wstrict-prototypes -fPIC -I/usr/include
> -I/usr/include/python2.6 -c meep_wrap.cpp -o
> build/temp.linux-x86_64-2.6/meep_wrap.o
> cc1plus: warning: command line option "-Wstrict-prototypes" is
> valid for Ada/C/ObjC but not for C++
> In file included from meep_wrap.cpp:3502:
> custom.hpp:39:30: error: numpy/npy_common.h: Nessun file o
> directory
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_deal_with_ctrl_c(PyObject*, PyObject*)’:
> meep_wrap.cpp:54701: warning: ‘argv[0]’ may be used
> uninitialized in this function
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_new_src_time(PyObject*, PyObject*)’:
> meep_wrap.cpp:28242: warning: ‘argv[0]’ may be used
> uninitialized in this function
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_new_symmetry(PyObject*, PyObject*)’:
> meep_wrap.cpp:15506: warning: ‘argv[0]’ may be used
> uninitialized in this function
> error: command 'gcc' failed with exit status 1
> Directories for SWIG -I option : ['/usr/include']
> Directories for -L option : ['/usr/lib']
> running install
> running build
> running build_py
> creating build/lib.linux-x86_64-2.6
> copying meep.py -> build/lib.linux-x86_64-2.6
> running build_ext
> building '_meep' extension
> swigging meep.i to meep_wrap.cpp
> swig -python -c++ -w503,389,302,362,314,509,451 -I/usr/include
> -o meep_wrap.cpp meep.i
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2
> -Wall -Wstrict-prototypes -fPIC -I/usr/include
> -I/usr/include/python2.6 -c meep_wrap.cpp -o
> build/temp.linux-x86_64-2.6/meep_wrap.o
> cc1plus: warning: command line option "-Wstrict-prototypes" is
> valid for Ada/C/ObjC but not for C++
> In file included from meep_wrap.cpp:3502:
> custom.hpp:39:30: error: numpy/npy_common.h: Nessun file o
> directory
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_deal_with_ctrl_c(PyObject*, PyObject*)’:
> meep_wrap.cpp:54701: warning: ‘argv[0]’ may be used
> uninitialized in this function
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_new_src_time(PyObject*, PyObject*)’:
> meep_wrap.cpp:28242: warning: ‘argv[0]’ may be used
> uninitialized in this function
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_new_symmetry(PyObject*, PyObject*)’:
> meep_wrap.cpp:15506: warning: ‘argv[0]’ may be used
> uninitialized in this function
> error: command 'gcc' failed with exit status 1
> Directories for SWIG -I option : ['/usr/include']
> Directories for -L option : ['/usr/lib']
> running bdist
> running bdist_dumb
> running build
> running build_py
> copying meep.py -> build/lib.linux-x86_64-2.6
> running build_ext
> building '_meep' extension
> swigging meep.i to meep_wrap.cpp
> swig -python -c++ -w503,389,302,362,314,509,451 -I/usr/include
> -o meep_wrap.cpp meep.i
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2
> -Wall -Wstrict-prototypes -fPIC -I/usr/include
> -I/usr/include/python2.6 -c meep_wrap.cpp -o
> build/temp.linux-x86_64-2.6/meep_wrap.o
> cc1plus: warning: command line option "-Wstrict-prototypes" is
> valid for Ada/C/ObjC but not for C++
> In file included from meep_wrap.cpp:3502:
> custom.hpp:39:30: error: numpy/npy_common.h: Nessun file o
> directory
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_deal_with_ctrl_c(PyObject*, PyObject*)’:
> meep_wrap.cpp:54701: warning: ‘argv[0]’ may be used
> uninitialized in this function
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_new_src_time(PyObject*, PyObject*)’:
> meep_wrap.cpp:28242: warning: ‘argv[0]’ may be used
> uninitialized in this function
> meep_wrap.cpp: In function ‘PyObject*
> _wrap_new_symmetry(PyObject*, PyObject*)’:
> meep_wrap.cpp:15506: warning: ‘argv[0]’ may be used
> uninitialized in this function
> error: command 'gcc' failed with exit status 1
> armaroli@armaroli-desktop:~/LATEST_RELEASE$
>
> If I ask locate npy_common.h, I only get the SAGE install
> path, local path that I was wondering if it could interfere
> with normal numpy install.
>
> Thank you.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~python-meep
> Post to : python-meep@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~python-meep
> More help : https://help.launchpad.net/ListHelp
References