Current Git broken?
1. hope this is the right forum for my problem.
2.
I'm compiling mscore-unstable, using the git source tree. Until yesterday, the make process was performed flawlessly. But since todya, mscore won't compile:
gmake stops after I made "git pull":
--------------------------------------------------------------------------------------
git pull
...
...
Generating moc_textproperties.cpp
Generating moc_textstyledialog.cpp
Generating moc_texttools.cpp
Generating moc_timedialog.cpp
Generating moc_timesigproperties.cpp
Generating moc_transposedialog.cpp
Generating moc_tremolobarcanvas.cpp
Generating moc_tremolobarprop.cpp
Generating moc_tupletdialog.cpp
Generating moc_updatechecker.cpp
Generating moc_uploadscoredialog.cpp
Generating moc_voltaproperties.cpp
Generating moc_waveview.cpp
Generating moc_workspace.cpp
make[3]: Leaving directory '/muse/MuseScore/build.release'
[ 0%] Built target mscore_automoc
make[2]: Leaving directory '/muse/MuseScore/build.release'
Makefile:149: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/muse/MuseScore/build.release'
Makefile:46: recipe for target 'release' failed
gmake: *** [release] Error 2
Anybody has a similar problem? My platform: Fedora 23, x86_64.
All these steps were performed flawlessly until yesterday.
Comments
You need to upgrade Qt to 5.6 and do a clean make after that
In reply to You need to upgrade Qt to 5.6 by Jojo-Schmitz
Hi Jojo,
all my qt5 pkgs have already version 5.6!
In reply to Hi Jojo, all my qt5 pkgs have by Joachim Backes
same problem in Fedora 24! Installed qt5-packages:
rpm -qa qt5*
qt5-qtscript-devel-5.6.0-3.fc24.x86_64
qt5-qtlocation-5.6.0-3.fc24.x86_64
qt5-qtquick1-5.6.0-3.fc24.x86_64
qt5-qttools-libs-help-5.6.0-3.fc24.x86_64
qt5-qttools-libs-designercomponents-5.6.0-3.fc24.x86_64
qt5-qtbase-gui-5.6.0-9.fc24.x86_64
qt5-qtwebchannel-5.6.0-3.fc24.x86_64
qt5-qtxmlpatterns-5.6.0-4.fc24.x86_64
qt5-designer-5.6.0-3.fc24.x86_64
qt5-qtdeclarative-devel-5.6.0-4.fc24.x86_64
qt5-qtwebkit-5.6.0-4.fc24.x86_64
qt5-qttools-libs-designer-5.6.0-3.fc24.x86_64
qt5-qtquickcontrols-5.6.0-3.fc24.x86_64
qt5-qtbase-common-5.6.0-9.fc24.noarch
qt5-qtscript-5.6.0-3.fc24.x86_64
qt5-rpm-macros-5.6.0-9.fc24.noarch
qt5-qtsvg-devel-5.6.0-3.fc24.x86_64
qt5-qtwebkit-devel-5.6.0-4.fc24.x86_64
qt5-qttools-libs-clucene-5.6.0-3.fc24.x86_64
qt5-qtbase-5.6.0-9.fc24.x86_64
qt5-qttools-5.6.0-3.fc24.x86_64
qt5-qtbase-devel-5.6.0-9.fc24.x86_64
qt5-qhelpgenerator-5.6.0-3.fc24.x86_64
qt5-qttools-static-5.6.0-3.fc24.x86_64
qt5-qtdeclarative-5.6.0-4.fc24.x86_64
qt5-qtsvg-5.6.0-3.fc24.x86_64
qt5-linguist-5.6.0-3.fc24.x86_64
qt5-qtxmlpatterns-devel-5.6.0-4.fc24.x86_64
qt5-qtsensors-5.6.0-3.fc24.x86_64
qt5-qdoc-5.6.0-3.fc24.x86_64
qt5-qtquick1-devel-5.6.0-3.fc24.x86_64
qt5-qttools-common-5.6.0-3.fc24.noarch
qt5-qttools-devel-5.6.0-3.fc24.x86_64
In reply to You need to upgrade Qt to 5.6 by Jojo-Schmitz
I reinstalled the complete source tree again with " git clone git://github.com/musescore/MuseScore.git", but if running make, I get the same error messages!
Between today and yesterday we merged a big pull request. See http://dev-list.musescore.org/Towards-MuseScore-3-td7579817.html
Can you post the full log on http://paste.kde.org or something similar?
PS: the best forum would be https://musescore.org/en/forum/687
In reply to Between today and yesterday by [DELETED] 5
You can download the full log (using the screen command) by
wget http://www-user.rhrk.uni-kl.de/~backes/DL/mscore.sc
In reply to You can download the full log by Joachim Backes
You miss QWebEngineView. The revelant line is
QWebEngineView: No such file or directory
#include
compilation terminated.
In reply to Between today and yesterday by [DELETED] 5
That single huge PR leaves MuseScore uncompilable even on Debian Testing. That's, errr, unfortunate. Qt5.6 is only available in Debian Experimental (maked rc-buggy).
Did this have to happen in one big chunk? (That's often a sign of unelegant version control handling ).
In reply to That single huge PR leaves by rmattes
Sometimes big changes need to happen, elegant or not. MuseScore is a big project and to push it forward we need to make big pushes from time to time.
Regarding Qt 5.6, you can download it on Qt website https://www.qt.io/download-open-source/ and it should work on all Debian.
An nightly AppImage of the current master for x86_64 should be available soon.
In reply to Sometimes big changes need to by [DELETED] 5
Yes, but this single PR/commit combines a lot of different features/changes. This is exactly how git is not supposed to be used. In case of a bug (an there will be some) git bisect will just shamefully point at that huge hunk of changes ... not very helpful.
BTW - I know how to build against current Qt5, and in theory it does work, except:
{syntaxhighlighter shell}
[ 0%] Generating all.h.gch
In file included from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtCore/qnamespace.h:37:0,
from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtCore/qobjectdefs.h:41,
from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtCore/qobject.h:40,
from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtCore/qabstractanimation.h:37,
from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtCore/QtCore:4,
from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtGui/QtGuiDepends:3,
from /opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtGui/QtGui:3,
from all.h:33:
/opt/Qt/Qt5.6.0/5.6/gcc_64/include/QtCore/qglobal.h:1090:4: error: #error "You must build your code with position independent code if Qt was built with -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not enough)."
# error "You must build your code with position independent code if Qt was built with -reduce-relocations. "\
^
CMakeFiles/mops2.dir/build.make:60: recipe for target 'all.h.gch' failed
make[2]: *** [all.h.gch] Error 1
CMakeFiles/Makefile2:200: recipe for target 'CMakeFiles/mops2.dir/all' failed
make[1]: *** [CMakeFiles/mops2.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
{/syntaxhighlighter}
Is this really up for the master branch?
In reply to Yes, but this single by rmattes
Thank you for the git lesson...
The master branch currently build and run successfully on Mac OSX, Windows and Ubuntu 12.04 Precise (our CI environment). I can't imagine it can't build on Debian Testing. Where is your Qt from?
In reply to Thank you for the git by [DELETED] 5
Fresh download from the official Qt website (the offline installer qt-opensource-linux-x64-5.6.0.run).
The reported problem seems to be a CMake problem (I'm using the CMake Support as provided by the Qt installation). The '-fPIC' flag is missing in CMAKE_CXX_FLAGS and CMAKE_CXX_FLAGS_DEBUG).
In reply to Fresh download from the by rmattes
If you're running Windows you might find my 5.4 to 5.6 upgrade docs/images helpful. See here: https://musescore.org/en/node/106326
I just realized it left out the steps I took with my env variables, like PATH anc CXX. Now I have to add those... but they are the same steps as in the standard compile instructions.
I have just successfully built and deployed today's MuseScore/master as of a few minutes ago.
In reply to If you're running Windows you by sideways
If you look at my last post you will see that I'm running Debian which is not windows.
In reply to Fresh download from the by rmattes
After fixing the compiler flags MuseScore does build.
Alas, (Lute) tablature seems to be completely broken, some of my tests create instant segfaults,
others just look weird.
In reply to After fixing the compiler by rmattes
I cannot reproduce the result of your attached image.
I receive presently an expected result (Tab for lute 13-course). See attachment.
Feel free to provide precise steps in the Issue Tracker for reproduce what you get (the "broken tab")
In reply to I cannot reproduce the result by cadiz1
Newly created tabs seem to work - opening some old samples created that broken rendering. I'm trying to find that sample but currently most of my samples trigger a segfault in libmscore/staff.cpp:748:
{syntaxhighlighter shell}
Program received signal SIGSEGV, Segmentation fault.
Ms::Staff::lines (this=this@entry=0x0) at /usr/local/src/MuseScore/libmscore/staff.cpp:748
748 return _staffType.lines();
(gdb) l
743 // lines
744 //---------------------------------------------------------
745
746 int Staff::lines() const
747 {
748 return _staffType.lines();
749 }
750
751 //---------------------------------------------------------
752 // setLines
{/syntaxhighlighter}
In reply to I cannot reproduce the result by cadiz1
I was wrong about newly created tabs. If I enter a minimal sample it seems to work, but reloading the document (see attachment) will result in tablature without lines. Selecting the screenshot tool seems to trigger a redraw but the result still has artefacts (see screenshot).
So far, the pdf export seems to work fine.
In reply to I was wrong about newly by rmattes
Ok, the problem is in Continuous View. I fill out a report soon (it is best not to deviate from the original topic now)
In reply to Yes, but this single by rmattes
It might be a lot of different commits, but it's basically one big change - a radically changed layout algorithm that you'll be hearing much more about soon. So it's not necessarily a bad thing that any bug introduced by this points to that one commit.
OS: Manjaro / Arch Linux
Problem: Compilation complained about Qt5WebEngineWidgets.
Everything worked fine until a few days ago.
I was able to fix this by installing qt5-webengine. For those who use pacman as their package manager:
sudo pacman -S qt5-webengine
In reply to OS: Manjaro / Arch by Fyrult
indeed QWebEngine is now a requirement on anything but MinGW
In reply to OS: Manjaro / Arch by Fyrult
Hi Fyruit,
this was very helpful. Now, I can compile the git-source in Fedora too after installing qt5*webengine*.
Thanks!
In reply to Hi Fyruit, this was very by Joachim Backes
Fedora users, would you mind updating this page? https://musescore.org/en/developers-handbook/compilation/compile-instru…
We don't have a arch page, but if you think it's valuable, don't hesitate to create one as a child page here https://musescore.org/en/developers-handbook/compilation
In reply to Fedora users, would you mind by [DELETED] 5
I added some update to https://musescore.org/en/developers-handbook/compilation/compile-instru… (pls. see diff), concening qt5-webengine.
JB