block 571491 by 571519
thanks
I think I can close 571491 now. This will be safe once 571519 is
closed (adding block).
--
Mathieu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 571491 vtk
thanks
Ok here is the summary.
In order to build the VTK-GDCM extension, GDCM needs a pre-installed
copy of VTK on the target machine. In this case a VTK 5.4 compiled
against python2.5 was found.
When building the VTK-GDCM extension, GDCM does not do anything bug
simply
to reproduce bug #571491.
Thanks,
Ps: Please note that gdcm Build-Dep on python-dev:
http://svn.debian.org/wsvn/debian-med/trunk/packages/gdcm/trunk/debian/control
PPs: as a side note this is not related to gdcm at all, but instead
vtk package. So I am CCing the vtk-guru too
(*)
On Thu, Feb 25, 2010
to python2.6
Stop using alternatives, make /usr/bin/python direct symlink to
python2.6, and it will work.
Could someone please let me know how I can change the default python
default version, or at least try to reproduce bug #571491.
FYI, after the failed build:
$ find -name 'flags.make
Source: gdcm
Version: 2.0.14-4
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python2.6
Hello,
When rebuilt in an environment with Python 2.6 as the default version,
your package failed to build from source. Here are the relevant parts of
the build log:
| make[3]:
5 matches
Mail list logo
