|
From: Henk K. <h....@cy...> - 2007-07-25 23:09:58
|
Dear all,
please help me on this one.. on a SuSE 10.1 linux machine with
Python 2.4.2. After a clean (i.e. everything is there):
$ ~/python/build> ../visual-3.2.9/configure --prefix=/usr
and
$ ~/python/build> make --debug
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
.
.
make[1]: Entering directory `/usr15/hk/python/build/src'
Updating dependancy information
for ../../visual-3.2.9/src/xgl.cpp ...
Updating dependancy information
for ../../visual-3.2.9/src/platlinux.cpp ...
.
.
Updating dependancy information
for ../../visual-3.2.9/src/arrow.cpp ...
make[1]: Leaving directory `/usr15/hk/python/build/src'
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Reading makefiles...
Updating goal targets....
File `all' does not exist.
File `log_message' does not exist.
Must remake target `log_message'.
make[1]: Entering directory `/usr15/hk/python/build/src'
This is a quiet Makefile. If make exits with an error, check
src/build.log to see the complete error message(s). In the event of
an error that you cannot debug, please send a message to
vis...@li..., including the files
config.log and src/build.log, requesting assistance.
Successfully remade target file `log_message'.
File `/home/hk/python/build/site-packages/cvisualmodule.la' does
not exist.
File `cvisualmodule.la' does not exist.
File `arrow.lo' does not exist.
Must remake target `arrow.lo'.
Compiling ../../visual-3.2.9/src/arrow.cpp ...
make[1]: *** [arrow.lo] Error 1
make[1]: Leaving directory `/usr15/hk/python/build/src'
make: *** [all-recursive] Error 1
$ ~/python/build>
What goes wrong here???
Then I grabbed visual-4.beta16. Here configure fails on Numpy:
...
checking for python script directory...
${prefix}/lib/python2.4/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.4/site-packages
checking for array in python module numpy... no
configure: error: The numpy module could not be found but is
required. See numpy.sourceforge.net for downloads.
Not on the module (it's there vs. 1.0.3.0) but on the blas-lib:
configure:19565: checking for array in python module numpy
Traceback (most recent call last):
File "<string>", line 1, in ?
File "/usr/lib/python2.4/site-packages/numpy/__init__.py", line
43, in ?
import linalg
File "/usr/lib/python2.4/site-packages/numpy/linalg/__init__.py",
line 4, in ?
from linalg import *
File "/usr/lib/python2.4/site-packages/numpy/linalg/linalg.py",
line 25, in ?
from numpy.linalg import lapack_lite
ImportError: /usr/lib/libblas.so.3: undefined symbol:
_gfortran_st_write
configure:19592: result: no
configure:19599: error: The numpy module could not be found but is
required. See numpy.sourceforge.net for downloads.
So a no go here either (blas is
installed, /usr/lib/libblas.so.3.0.0, but want's to write with
fortran).
Thanks!
Henk
PS: I'm relatively new to Python (played a bit with Tkinter in a
simple code called Orka). My interest is to use Python along with
OpenGL (easily, drawing meshes and results so no fancy stuff like
'fog', 'textures' but with 'picking displayed items' -as described
in the Red Book with Glut-) and the interface to f95/g95/f03 so
(major) parts can be handled in fortran but python can access the
(geometry)data in the main modules. And maybe I can write into the
VPython generated canvas from fortran as well (as long as one
passes the window id, why not?).
|
|
From: Bruce S. <Bru...@nc...> - 2007-07-26 01:37:13
|
Not possible to guess what went wrong with the make of the standard
version without seeing the build.log in the src directory, which gives
details.
As for the beta version, again it's difficult to diagnose from what you
report, but perhaps not all the numpy pieces are in fact installed?
Including the dev component?
Bruce Sherwood
Henk Krus wrote:
> Dear all,
>
> please help me on this one.. on a SuSE 10.1 linux machine with
> Python 2.4.2. After a clean (i.e. everything is there):
>
> $ ~/python/build> ../visual-3.2.9/configure --prefix=/usr
>
> and
>
> $ ~/python/build> make --debug
> GNU Make 3.80
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> .
> .
> make[1]: Entering directory `/usr15/hk/python/build/src'
> Updating dependancy information
> for ../../visual-3.2.9/src/xgl.cpp ...
> Updating dependancy information
> for ../../visual-3.2.9/src/platlinux.cpp ...
> .
> .
> Updating dependancy information
> for ../../visual-3.2.9/src/arrow.cpp ...
> make[1]: Leaving directory `/usr15/hk/python/build/src'
> GNU Make 3.80
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
> Reading makefiles...
> Updating goal targets....
> File `all' does not exist.
> File `log_message' does not exist.
> Must remake target `log_message'.
> make[1]: Entering directory `/usr15/hk/python/build/src'
> This is a quiet Makefile. If make exits with an error, check
> src/build.log to see the complete error message(s). In the event of
> an error that you cannot debug, please send a message to
> vis...@li..., including the files
> config.log and src/build.log, requesting assistance.
> Successfully remade target file `log_message'.
> File `/home/hk/python/build/site-packages/cvisualmodule.la' does
> not exist.
> File `cvisualmodule.la' does not exist.
> File `arrow.lo' does not exist.
> Must remake target `arrow.lo'.
> Compiling ../../visual-3.2.9/src/arrow.cpp ...
> make[1]: *** [arrow.lo] Error 1
> make[1]: Leaving directory `/usr15/hk/python/build/src'
> make: *** [all-recursive] Error 1
> $ ~/python/build>
>
> What goes wrong here???
>
> Then I grabbed visual-4.beta16. Here configure fails on Numpy:
>
> ...
> checking for python script directory...
> ${prefix}/lib/python2.4/site-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.4/site-packages
> checking for array in python module numpy... no
> configure: error: The numpy module could not be found but is
> required. See numpy.sourceforge.net for downloads.
>
> Not on the module (it's there vs. 1.0.3.0) but on the blas-lib:
>
> configure:19565: checking for array in python module numpy
> Traceback (most recent call last):
> File "<string>", line 1, in ?
> File "/usr/lib/python2.4/site-packages/numpy/__init__.py", line
> 43, in ?
> import linalg
> File "/usr/lib/python2.4/site-packages/numpy/linalg/__init__.py",
> line 4, in ?
> from linalg import *
> File "/usr/lib/python2.4/site-packages/numpy/linalg/linalg.py",
> line 25, in ?
> from numpy.linalg import lapack_lite
> ImportError: /usr/lib/libblas.so.3: undefined symbol:
> _gfortran_st_write
> configure:19592: result: no
> configure:19599: error: The numpy module could not be found but is
> required. See numpy.sourceforge.net for downloads.
>
> So a no go here either (blas is
> installed, /usr/lib/libblas.so.3.0.0, but want's to write with
> fortran).
>
> Thanks!
> Henk
>
> PS: I'm relatively new to Python (played a bit with Tkinter in a
> simple code called Orka). My interest is to use Python along with
> OpenGL (easily, drawing meshes and results so no fancy stuff like
> 'fog', 'textures' but with 'picking displayed items' -as described
> in the Red Book with Glut-) and the interface to f95/g95/f03 so
> (major) parts can be handled in fortran but python can access the
> (geometry)data in the main modules. And maybe I can write into the
> VPython generated canvas from fortran as well (as long as one
> passes the window id, why not?).
>
>
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
|
|
From: Henk K. <h....@cy...> - 2007-07-26 07:54:56
|
Op donderdag 26 juli 2007 03:37, schreef u: > Not possible to guess what went wrong with the make of the > standard version without seeing the build.log in the src > directory, which gives details. > Thanks for pointing to this log: "boost" is missing ... ../../visual-3.2.9/include/cvisual.h:8:47: error: boost/python/detail/wrap_python.hpp: No such file or directory ../../visual-3.2.9/include/cvisual.h:12:34: error: boost/python/tuple.hpp: No such file or directory ../../visual-3.2.9/include/cvisual.h:13:33: error: boost/python/list.hpp: No such file or directory In file included from ../../visual-3.2.9/include/prim.h:8, > As for the beta version, again it's difficult to diagnose from > what you report, but perhaps not all the numpy pieces are in fact > installed? Including the dev component? > numpy relies on blas/libblas so I installed it with suse's yast. However suse's blas seems to contain a fortran-write statement to stdout/unit 6/* which cannot be resolved: > > "/usr/lib/python2.4/site-packages/numpy/linalg/linalg.py", line > > 25, in ? > > from numpy.linalg import lapack_lite > > ImportError: /usr/lib/libblas.so.3: undefined symbol: > > _gfortran_st_write > > configure:19592: result: no > > configure:19599: error: The numpy module could not be found but > > is required. See numpy.sourceforge.net for downloads. > > hunting down blas, recompiling lapack is not that difficult, when lapack is all what has to to be compiled (hm I see a leading underscore... underscore usage in the lib usage maybe needs some attention as well). I will go after boost first. Thanks. Henk |
|
From: Henk K. <h....@cy...> - 2007-07-26 15:00:40
|
Dear all, it was the missing 'boost' (configure missed it) after downloading from boost.org and a very long session I was able to 'move' libboost_python.so to /usr/lib (libboost_python-gcc41-1_34_1.so.1.34.1) and copy the boost-includes to /usr/local/include/boost/. Hitting 'make' again and 'make install' and I was able to run all the demos in /usr/lib/python2.4/site-packages/visual/examples without any problems. Now it's time to study vpython more in detail. Thanks! Henk Op donderdag 26 juli 2007 10:06, schreef Henk Krus: > Op donderdag 26 juli 2007 03:37, schreef u: > > Not possible to guess what went wrong with the make of the > > standard version without seeing the build.log in the src > > directory, which gives details. > > Thanks for pointing to this log: "boost" is missing > |