~/applications/bin/root/build/bin/root.exe does not exist (unsurprisingly). I don’t understand why this is happening. Any thoughts or suggestions would be greatly appreciated.
Mato, I pulled from git this morning (2016-01-31) to try again and am still encountering the same problems. Should I expect that the dependency should be ready to be pulled by tomorrow morning?
From what you say, it seems that ROOT (via cmake) detected qt4 and did not find qt3 support.
This should NOT be possible.
On Ubuntu 14.04, qt3 binary support is part of the “libqt4-qt3support” package which will automatically be installed by the “libqt4-dev” package (i.e. as soon as “development” files for qt4 are there also the qt3 support, including “development” files, is there).
So, it is NOT possible that qt3 support is missing when qt4 support is there.
Looking at my “CMakeCache.txt” for ROOT v6-06-00, I have:
QT_QT3SUPPORT_INCLUDE_DIR:PATH=/usr/include/qt4/Qt3Support
QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1
After pulling the latest version from git I am now able to get farther, but I still get an error that kills the build. I did a double check and have confirmed that all the required and optional prerequisite packages installed.
My build commands:
Does your installation of Qt4 has a support for Qt3? In other words does the file is looking (q3vbox.h) for exists in our installation under /home/mcf/anaconda/…?
I think there is a potential caveat … in my setup, q4 is the “default”, so I cannot test it … however, if you make qt5 the “default” and install qt5 with its “development” files, then there is probably a qt4 compatibility layer included (at least some “partial”?), but possibly qt3 compatibility is dropped completely (so ROOT detects qt4 and a missing qt3).
Hi,
I build root git from xenial 16.04, I guess with recent ubuntu it should work too ?
I got the source this way : git clone root.cern.ch/git/root.git, before compiling it’s better to try to get necessary most libs this way :
sudo apt-get build dep root
You should have to install quiet a lot ?
cd root
./configure && make j-9
(j-9 for me because I have a core 8 +1) so adapt to yours …
when finised just run root
I use ipython /jupyter notebook with rootpy so I made a link
sudo ln -s root/root /usr/bin/root
(adapt to your path too… For me it’s sudo ln -s /home/riri/root/root /usr/bin/root
and then if you type root from your home it should work.
I had no problem at all installing it this way.
Another method is installing root-system ver. 5.34 from repo, but if you do so after you might have problems if you want to compile it later. For most work it’s enaught but not for jupyter notebook.
Kind regards
Henri
I apologize that I am completely ignorant to the subtleties of the problem at the moment, but I appreciate your continued help.
Henri, thank you for your suggestion, however, I am trying to do this build without relying on the ROOT 5 way of doing thins with ./configure, as it seems that the future of LTS with ROOT will be with CMake. Please feel free to correct me if I am making an incorrect assumption. dpkg_list.out.txt (17.4 KB)
It seems to me that you have all required system packages installed.
Looking at your “cmake.out.txt” file again, you seem to have another qt4 version installed in “/home/mcf/anaconda/…” (there’s the “/home/mcf/anaconda/bin/qmake” which reports qt “4.8.7”). I think you need to get rid of it completely (so that the system default qt4 version is used) or you need to install some additional anaconda qt3 backwards compatibility related packages to your new qt “4.8.7”.
I’m not sure what Qt actually does in terms of graphics (is it what actually runs the graphics for GUIs like TBrowser?), so would disabling these build options likely cause further problems? I’m not unwilling to get rid of anaconda’s v of qt4, but I’d just prefer not to if possible.
You didn’t set “CMAKE_INSTALL_PREFIX” so you should not call “cmake … --target install” (you built ROOT “in-place” so don’t try to “install” it as the procedure may be broken somehow, you never know).
Note also: I think that, as soon as you set -Dqt=“OFF”, you do not need to set -Dqtgsi=“OFF” (it will be internally done automatically).