Therion 5.3.11 fails compile in Loch
Hello everyone - It has been several years since I went through the pain of compiling Therion. I remember that Loch has always given me trouble. Today I downloaded 5.3.11 and see that nothing has changed. Loch is still failing. Here is the last bits of output I get when running make: ======================= make -C ./loch make[1]: Entering directory `/Installs/therion-5.3.11/loch' c++ -o loch -Wall lxR2P.o lxTR.o lxOGLFT.o lxSetup.o lxRender.o lxWX.o lxImgIO.o lxLRUD.o lxFile.o lxSTree.o lxData.o lxMath.o lxSView.o lxSScene.o lxGUI.o lxGLC.o lxOptDlg.o lxAboutDlg.o img.o -lwx_gtk2u_gl-2.8 -pthread -Wl,- z,relro -lwx_gtk2u_richtext-2.8 -lwx_gtk2u_aui-2.8 -lwx_gtk2u_xrc-2.8 - lwx_gtk2u_qa-2.8 -lwx_gtk2u_html-2.8 -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 - lwx_baseu_xml-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8 -L/usr/lib/vtk-5.4 - lvtkHybrid -lvtkImaging -lvtkIO -lvtkGraphics -lvtkFiltering -lvtkCommon - lfreetype -lGLU -lpthread -lz -s /usr/bin/ld: cannot find -lvtkHybrid /usr/bin/ld: cannot find -lvtkImaging /usr/bin/ld: cannot find -lvtkIO /usr/bin/ld: cannot find -lvtkGraphics /usr/bin/ld: cannot find -lvtkFiltering /usr/bin/ld: cannot find -lvtkCommon collect2: error: ld returned 1 exit status make[1]: *** [loch] Error 1 make[1]: Leaving directory `/Installs/therion-5.3.11/loch' make: *** [loch/loch] Error 2 ==================== The system is 64-bit Fedora 17. I suspect the problem is in the command line option "-L/usr/lib/vtk-5.4". The system by default does not have this directory. I added a symbolic link to the location of vtk (/usr/include/vtk-5.4) but it made no difference. I have never used Loch. Is there a command line option to tell make to skip Loch? Somehow I got past this with Therion 5.3.6, but I do not remember how. Thanks - Bill Gee
On Mon, Oct 07, 2013 at 08:16:31PM -0500, Bill Gee wrote:
The system is 64-bit Fedora 17.
I suspect the problem is in the command line option "-L/usr/lib/vtk-5.4". The system by default does not have this directory. I added a symbolic link to the location of vtk (/usr/include/vtk-5.4) but it made no difference.
"/usr/include" is not the directory you are looking for (it's for headers rather than libraries). You probably want "/usr/lib64/vtk-5.4" on 64-bit Fedora.
I have never used Loch. Is there a command line option to tell make to skip Loch?
Looks like this might work, but I've not tested it: make LOCHEXE= Cheers, Olly
Apologies for mailing the list, but Bill's email setup is rejecting email from me, which he probably should know about: | bgee@campercaver.net | SMTP error from remote mail server after RCPT TO:<bgee@campercaver.net>: | host mail.campercaver.net [65.70.157.120]: 554 5.7.1 <atreus.tartarus.org[80.252.125.10]>: | Client host rejected: Access denied Cheers, Olly
Hi, To build therion on debian, I install first packages below: wx2.8-headers libwxgtk2.8-dev wx-common mesa-common-dev libglu1-mesa-dev libfreetype6-dev libvtk5-dev Regards, C.S. 2013/10/8 Bill Gee <bgee@campercaver.net>
Hello everyone -
It has been several years since I went through the pain of compiling Therion. I remember that Loch has always given me trouble. Today I downloaded 5.3.11 and see that nothing has changed. Loch is still failing.
Here is the last bits of output I get when running make:
=======================
make -C ./loch make[1]: Entering directory `/Installs/therion-5.3.11/loch' c++ -o loch -Wall lxR2P.o lxTR.o lxOGLFT.o lxSetup.o lxRender.o lxWX.o lxImgIO.o lxLRUD.o lxFile.o lxSTree.o lxData.o lxMath.o lxSView.o lxSScene.o lxGUI.o lxGLC.o lxOptDlg.o lxAboutDlg.o img.o -lwx_gtk2u_gl-2.8 -pthread -Wl,- z,relro -lwx_gtk2u_richtext-2.8 -lwx_gtk2u_aui-2.8 -lwx_gtk2u_xrc-2.8 - lwx_gtk2u_qa-2.8 -lwx_gtk2u_html-2.8 -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 - lwx_baseu_xml-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8 -L/usr/lib/vtk-5.4 - lvtkHybrid -lvtkImaging -lvtkIO -lvtkGraphics -lvtkFiltering -lvtkCommon - lfreetype -lGLU -lpthread -lz -s /usr/bin/ld: cannot find -lvtkHybrid /usr/bin/ld: cannot find -lvtkImaging /usr/bin/ld: cannot find -lvtkIO /usr/bin/ld: cannot find -lvtkGraphics /usr/bin/ld: cannot find -lvtkFiltering /usr/bin/ld: cannot find -lvtkCommon collect2: error: ld returned 1 exit status make[1]: *** [loch] Error 1 make[1]: Leaving directory `/Installs/therion-5.3.11/loch' make: *** [loch/loch] Error 2
====================
The system is 64-bit Fedora 17.
I suspect the problem is in the command line option "-L/usr/lib/vtk-5.4". The system by default does not have this directory. I added a symbolic link to the location of vtk (/usr/include/vtk-5.4) but it made no difference.
I have never used Loch. Is there a command line option to tell make to skip Loch?
Somehow I got past this with Therion 5.3.6, but I do not remember how.
Thanks - Bill Gee _______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
+++ cawa sorix [2013-10-08 08:17 +0200]:
Hi,
To build therion on debian, I install first packages below: wx2.8-headers libwxgtk2.8-dev wx-common mesa-common-dev libglu1-mesa-dev libfreetype6-dev libvtk5-dev
And the packaging adds $(VTKLIBS) to PLIBS in the makefile: --- therion-5.3.11.orig/loch/Makefile 2013-09-03 03:59:17.912863415 +0100 +++ therion-5.3.11/loch/Makefile 2013-09-06 03:07:56.662776189 +0100 @@ -33,10 +33,10 @@ CC = gcc POBJECTS = lxR2P.o VTKLIBS = -lvtkHybrid -lvtkImaging -lvtkIO -lvtkGraphics -lvtkFiltering -lvtkCommon -lfreetype -CXXPFLAGS = -DLXLINUX $(shell wx-config --cxxflags) -Wno-deprecated $(shell freetype-config --cflags) -I$(VTKPATH) +CXXPFLAGS = -DLXLINUX $(shell wx-config --cxxflags) $(shell freetype-config --cflags) -I$(VTKPATH) CCPFLAGS = -DLXLINUX $(shell wx-config --cflags) LXLIBDIR = linux -PLIBS = $(shell wx-config --libs --gl-libs) -L$(VTKLIBPATH) $(VTKLIBS) -lGLU -lpthread -lz +PLIBS = $(shell wx-config --libs --gl-libs) $(VTKLIBS) -lpthread -lz $(shell pkg-config --libs libpng glu) -ljpeg -lX11 LXPLATFORM = LINUX # PLATFORM WIN32
I suspect the problem is in the command line option "-L/usr/lib/vtk-5.4". �The system by default does not have this directory. �I added a symbolic link to the location of vtk (/usr/include/vtk-5.4) but it made no difference.
Debian is up to vtk-5.8. I'd expect Fedora to have a newer version by now too? But the makefile in 5.3.11 doesn't actually specify an explicit version any more. It uses: VTKVERSION = $(shell tclsh ./getvtkver.tcl version) I guess RPMworld needs a caving packager :-) Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/
Hi Wookey - It is kind of a strange situation for me. I earn a good living as a software packager for Windows applications. I can turn MSI files inside-out. But RPMs?? I have no clue where to even start! Of course, if I were to take on RPM packaging, I still have to get Therion to compile. Fedora 17 is over a year old. They are up to 19, and I expect to see 20 before the end of the year. Still, it's not THAT old. On that subject - Fedora package names are quite different from Debian. I ran some queries on my system to see what is installed. Here is what it shows. I think this covers everything you mentioned. ================ [bgee@main2 ~]$ rpm -qa | grep -i wx wxGTK-devel-2.8.12-4.fc17.x86_64 wxPython-2.8.12.0-2.fc17.x86_64 wxBase-2.8.12-4.fc17.x86_64 wxGTK-2.8.12-4.fc17.x86_64 wxGTK-media-2.8.12-4.fc17.x86_64 wxGTK-gl-2.8.12-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i mesa mesa-libGL-devel-8.0.4-1.fc17.x86_64 mesa-libOSMesa-devel-8.0.4-1.fc17.x86_64 mesa-libglapi-8.0.4-1.fc17.x86_64 mesa-libxatracker-8.0.4-1.fc17.x86_64 mesa-libOSMesa-8.0.4-1.fc17.x86_64 mesa-dri-filesystem-8.0.4-1.fc17.x86_64 mesa-libGLU-8.0.4-1.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 mesa-libgbm-8.0.4-1.fc17.x86_64 mesa-libEGL-8.0.4-1.fc17.x86_64 mesa-libGLU-devel-8.0.4-1.fc17.x86_64 mesa-libGLES-8.0.4-1.fc17.x86_64 mesa-libGL-8.0.4-1.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i freetype freetype-2.4.8-4.fc17.x86_64 freetype-2.4.8-4.fc17.i686 freetype-devel-2.4.8-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i vtk vtk-tcl-5.8.0-6.fc17.x86_64 vtk-5.8.0-6.fc17.x86_64 vtk-python-5.8.0-6.fc17.x86_64 vtk-devel-5.8.0-6.fc17.x86_64 vtk-qt-5.8.0-6.fc17.x86_64 vtk-java-5.8.0-6.fc17.x86_64 [bgee@main2 ~]$ ===================== I assume xTherion needs vtk .... If vtk were the problem, then I would expect the Therion compiles to fail too. It runs through xTherion without error. It only fails when it gets to Loch. Regards - Bill Gee On Tuesday, October 08, 2013 10:16:34 Wookey wrote:
+++ cawa sorix [2013-10-08 08:17 +0200]:
Hi,
To build therion on debian, I install first packages below: wx2.8-headers libwxgtk2.8-dev wx-common mesa-common-dev libglu1-mesa-dev libfreetype6-dev libvtk5-dev
And the packaging adds $(VTKLIBS) to PLIBS in the makefile:
--- therion-5.3.11.orig/loch/Makefile 2013-09-03 03:59:17.912863415 +0100 +++ therion-5.3.11/loch/Makefile 2013-09-06 03:07:56.662776189 +0100 @@ -33,10 +33,10 @@ CC = gcc POBJECTS = lxR2P.o VTKLIBS = -lvtkHybrid -lvtkImaging -lvtkIO -lvtkGraphics -lvtkFiltering -lvtkCommon -lfreetype -CXXPFLAGS = -DLXLINUX $(shell wx-config --cxxflags) -Wno-deprecated $(shell freetype-config --cflags) -I$(VTKPATH) +CXXPFLAGS = -DLXLINUX $(shell wx-config --cxxflags) $(shell freetype-config --cflags) -I$(VTKPATH) CCPFLAGS = -DLXLINUX $(shell wx-config --cflags) LXLIBDIR = linux -PLIBS = $(shell wx-config --libs --gl-libs) -L$(VTKLIBPATH) $(VTKLIBS) -lGLU -lpthread -lz +PLIBS = $(shell wx-config --libs --gl-libs) $(VTKLIBS) -lpthread -lz $(shell pkg-config --libs libpng glu) -ljpeg -lX11 LXPLATFORM = LINUX
# PLATFORM WIN32
I suspect the problem is in the command line option "-L/usr/lib/vtk-5.4". �The system by default does not have this directory. �I added a symbolic link to the location of vtk (/usr/include/vtk-5.4) but it made no difference.
Debian is up to vtk-5.8. I'd expect Fedora to have a newer version by now too? But the makefile in 5.3.11 doesn't actually specify an explicit version any more. It uses: VTKVERSION = $(shell tclsh ./getvtkver.tcl version)
I guess RPMworld needs a caving packager :-)
Wookey
+++ Bill Gee [2013-10-08 19:42 -0500]:
Hi Wookey -
It is kind of a strange situation for me. I earn a good living as a software packager for Windows applications. I can turn MSI files inside-out. But RPMs?? I have no clue where to even start!
Right well, maybe you can help with the windows packaging (although we do it using Linux tools).
Of course, if I were to take on RPM packaging, I still have to get Therion to compile.
Fedora 17 is over a year old. They are up to 19, and I expect to see 20 before the end of the year. Still, it's not THAT old.
On that subject - Fedora package names are quite different from Debian.
Yes, that's often the case. There is a different set of conventions.
I ran some queries on my system to see what is installed. Here is what it shows. I think this covers everything you mentioned. ================
[bgee@main2 ~]$ rpm -qa | grep -i wx wxGTK-devel-2.8.12-4.fc17.x86_64 wxPython-2.8.12.0-2.fc17.x86_64 wxBase-2.8.12-4.fc17.x86_64 wxGTK-2.8.12-4.fc17.x86_64 wxGTK-media-2.8.12-4.fc17.x86_64 wxGTK-gl-2.8.12-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i mesa mesa-libGL-devel-8.0.4-1.fc17.x86_64 mesa-libOSMesa-devel-8.0.4-1.fc17.x86_64 mesa-libglapi-8.0.4-1.fc17.x86_64 mesa-libxatracker-8.0.4-1.fc17.x86_64 mesa-libOSMesa-8.0.4-1.fc17.x86_64 mesa-dri-filesystem-8.0.4-1.fc17.x86_64 mesa-libGLU-8.0.4-1.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 mesa-libgbm-8.0.4-1.fc17.x86_64 mesa-libEGL-8.0.4-1.fc17.x86_64 mesa-libGLU-devel-8.0.4-1.fc17.x86_64 mesa-libGLES-8.0.4-1.fc17.x86_64 mesa-libGL-8.0.4-1.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i freetype freetype-2.4.8-4.fc17.x86_64 freetype-2.4.8-4.fc17.i686 freetype-devel-2.4.8-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i vtk vtk-tcl-5.8.0-6.fc17.x86_64 vtk-5.8.0-6.fc17.x86_64 vtk-python-5.8.0-6.fc17.x86_64 vtk-devel-5.8.0-6.fc17.x86_64 vtk-qt-5.8.0-6.fc17.x86_64 vtk-java-5.8.0-6.fc17.x86_64 [bgee@main2 ~]$
=====================
I assume xTherion needs vtk
No. Loch needs vtk and wx xtherion needs tcl and tk .... If vtk were the problem, then I would expect
the Therion compiles to fail too. It runs through xTherion without error. It only fails when it gets to Loch.
Exactly. Look at the difference between the top-level Makefile and the loch/Makefile. You can see a working (debian) build-log here, which might help: https://buildd.debian.org/status/fetch.php?pkg=therion&arch=i386&ver=5.3.11-... Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/
Hello everyone - It has been a couple of months. With the release of version 5.3.12 I dug into this problem in greater depth. Net result - I can get Therion to compile but Loch is still no-go. Details below. I don't use Loch, so not having it is not a problem for me. The target system is Fedora 20, 64-bit. I installed it as a clean, fresh system. It is not an upgrade. One thing I found with Fedora 20 is that vtk-devel cannot be installed. When I try to "yum install vtk-devel" I get a raft of errors that ends like this: --> Processing Conflict: community-mysql-5.5.34-1.fc20.x86_64 conflicts --> mariadb --> Processing Conflict: 1:mariadb-5.5.34-2.fc20.x86_64 conflicts --> community-mysql --> Finished Dependency Resolution Error: mariadb conflicts with community-mysql-5.5.34-1.fc20.x86_64 Error: community-mysql conflicts with 1:mariadb-5.5.34-2.fc20.x86_64 There is also a long list of dependencies that includes PostGreSQL and what looks like 50 or 60 Python and TCL libraries. It's a mess!!! Here is what I changed to make Therion compile. 1) In file "makeinstall.tcl" ... Comment out line 55. 2) In file "Makefile" ... Change line 122 to read all: therion doc xtherion/xtherion 3) In file "Makefile" ... Comment out lines 30, 173, 174, 190, 229, 233, 237, 241, 245, 249 The next thing I will do is try this on some systems that are upgraded from Fedora 19 to 20. Regards - Bill Gee On Thursday, October 17, 2013 17:21:43 Wookey wrote:
+++ Bill Gee [2013-10-08 19:42 -0500]:
Hi Wookey -
It is kind of a strange situation for me. I earn a good living as a software packager for Windows applications. I can turn MSI files inside-out. But RPMs?? I have no clue where to even start!
Right well, maybe you can help with the windows packaging (although we do it using Linux tools).
Of course, if I were to take on RPM packaging, I still have to get Therion to compile.
Fedora 17 is over a year old. They are up to 19, and I expect to see 20 before the end of the year. Still, it's not THAT old.
On that subject - Fedora package names are quite different from Debian.
Yes, that's often the case. There is a different set of conventions.
I ran some queries on my system to see what is installed. Here is what it shows. I think this covers everything you mentioned. ================
[bgee@main2 ~]$ rpm -qa | grep -i wx wxGTK-devel-2.8.12-4.fc17.x86_64 wxPython-2.8.12.0-2.fc17.x86_64 wxBase-2.8.12-4.fc17.x86_64 wxGTK-2.8.12-4.fc17.x86_64 wxGTK-media-2.8.12-4.fc17.x86_64 wxGTK-gl-2.8.12-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i mesa mesa-libGL-devel-8.0.4-1.fc17.x86_64 mesa-libOSMesa-devel-8.0.4-1.fc17.x86_64 mesa-libglapi-8.0.4-1.fc17.x86_64 mesa-libxatracker-8.0.4-1.fc17.x86_64 mesa-libOSMesa-8.0.4-1.fc17.x86_64 mesa-dri-filesystem-8.0.4-1.fc17.x86_64 mesa-libGLU-8.0.4-1.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 mesa-libgbm-8.0.4-1.fc17.x86_64 mesa-libEGL-8.0.4-1.fc17.x86_64 mesa-libGLU-devel-8.0.4-1.fc17.x86_64 mesa-libGLES-8.0.4-1.fc17.x86_64 mesa-libGL-8.0.4-1.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i freetype freetype-2.4.8-4.fc17.x86_64 freetype-2.4.8-4.fc17.i686 freetype-devel-2.4.8-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i vtk vtk-tcl-5.8.0-6.fc17.x86_64 vtk-5.8.0-6.fc17.x86_64 vtk-python-5.8.0-6.fc17.x86_64 vtk-devel-5.8.0-6.fc17.x86_64 vtk-qt-5.8.0-6.fc17.x86_64 vtk-java-5.8.0-6.fc17.x86_64 [bgee@main2 ~]$
=====================
I assume xTherion needs vtk
No. Loch needs vtk and wx
xtherion needs tcl and tk
.... If vtk were the problem, then I would expect
the Therion compiles to fail too. It runs through xTherion without error. It only fails when it gets to Loch.
Exactly. Look at the difference between the top-level Makefile and the loch/Makefile.
You can see a working (debian) build-log here, which might help: https://buildd.debian.org/status/fetch.php?pkg=therion&arch=i386&ver=5.3.11-> 2&stamp=1381462995
Wookey
Hi, you definitely need vtk-devel to be able to compile Loch. But vtk-devel depends on mysql-devel which condlicts with mariadb. MariaDB is for of MySQL. Try to uninstall (if possible) mariadb + mariadb devel package and try again \Ladislav 29. 12. 2013 v 22:04, Bill Gee <bgee@campercaver.net>:
Hello everyone -
It has been a couple of months. With the release of version 5.3.12 I dug into this problem in greater depth. Net result - I can get Therion to compile but Loch is still no-go. Details below. I don't use Loch, so not having it is not a problem for me.
The target system is Fedora 20, 64-bit. I installed it as a clean, fresh system. It is not an upgrade.
One thing I found with Fedora 20 is that vtk-devel cannot be installed. When I try to "yum install vtk-devel" I get a raft of errors that ends like this:
--> Processing Conflict: community-mysql-5.5.34-1.fc20.x86_64 conflicts --> mariadb --> Processing Conflict: 1:mariadb-5.5.34-2.fc20.x86_64 conflicts --> community-mysql --> Finished Dependency Resolution Error: mariadb conflicts with community-mysql-5.5.34-1.fc20.x86_64 Error: community-mysql conflicts with 1:mariadb-5.5.34-2.fc20.x86_64
There is also a long list of dependencies that includes PostGreSQL and what looks like 50 or 60 Python and TCL libraries. It's a mess!!!
Here is what I changed to make Therion compile.
1) In file "makeinstall.tcl" ... Comment out line 55.
2) In file "Makefile" ... Change line 122 to read
all: therion doc xtherion/xtherion
3) In file "Makefile" ... Comment out lines 30, 173, 174, 190, 229, 233, 237, 241, 245, 249
The next thing I will do is try this on some systems that are upgraded from Fedora 19 to 20.
Regards - Bill Gee
On Thursday, October 17, 2013 17:21:43 Wookey wrote: +++ Bill Gee [2013-10-08 19:42 -0500]:
Hi Wookey -
It is kind of a strange situation for me. I earn a good living as a software packager for Windows applications. I can turn MSI files inside-out. But RPMs?? I have no clue where to even start!
Right well, maybe you can help with the windows packaging (although we do it using Linux tools).
Of course, if I were to take on RPM packaging, I still have to get Therion to compile.
Fedora 17 is over a year old. They are up to 19, and I expect to see 20 before the end of the year. Still, it's not THAT old.
On that subject - Fedora package names are quite different from Debian.
Yes, that's often the case. There is a different set of conventions.
I ran some queries on my system to see what is installed. Here is what it shows. I think this covers everything you mentioned. ================
[bgee@main2 ~]$ rpm -qa | grep -i wx wxGTK-devel-2.8.12-4.fc17.x86_64 wxPython-2.8.12.0-2.fc17.x86_64 wxBase-2.8.12-4.fc17.x86_64 wxGTK-2.8.12-4.fc17.x86_64 wxGTK-media-2.8.12-4.fc17.x86_64 wxGTK-gl-2.8.12-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i mesa mesa-libGL-devel-8.0.4-1.fc17.x86_64 mesa-libOSMesa-devel-8.0.4-1.fc17.x86_64 mesa-libglapi-8.0.4-1.fc17.x86_64 mesa-libxatracker-8.0.4-1.fc17.x86_64 mesa-libOSMesa-8.0.4-1.fc17.x86_64 mesa-dri-filesystem-8.0.4-1.fc17.x86_64 mesa-libGLU-8.0.4-1.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 mesa-libgbm-8.0.4-1.fc17.x86_64 mesa-libEGL-8.0.4-1.fc17.x86_64 mesa-libGLU-devel-8.0.4-1.fc17.x86_64 mesa-libGLES-8.0.4-1.fc17.x86_64 mesa-libGL-8.0.4-1.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i freetype freetype-2.4.8-4.fc17.x86_64 freetype-2.4.8-4.fc17.i686 freetype-devel-2.4.8-4.fc17.x86_64 [bgee@main2 ~]$ rpm -qa | grep -i vtk vtk-tcl-5.8.0-6.fc17.x86_64 vtk-5.8.0-6.fc17.x86_64 vtk-python-5.8.0-6.fc17.x86_64 vtk-devel-5.8.0-6.fc17.x86_64 vtk-qt-5.8.0-6.fc17.x86_64 vtk-java-5.8.0-6.fc17.x86_64 [bgee@main2 ~]$
=====================
I assume xTherion needs vtk
No. Loch needs vtk and wx
xtherion needs tcl and tk
.... If vtk were the problem, then I would expect
the Therion compiles to fail too. It runs through xTherion without error. It only fails when it gets to Loch.
Exactly. Look at the difference between the top-level Makefile and the loch/Makefile.
You can see a working (debian) build-log here, which might help: https://buildd.debian.org/status/fetch.php?pkg=therion&arch=i386&ver=5.3.11-> 2&stamp=1381462995
Wookey
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
participants (5)
-
Bill Gee -
cawa sorix -
lada＠blazcata.cz -
Olly Betts -
Wookey