Re: master GIT broken?
On Tue, Feb 28, 2017 at 5:06 PM, Enrico Forestieriwrote: > On Tue, Feb 28, 2017 at 03:29:37PM +0100, Liviu Andronic wrote: > > This doesn't look right, as user: > > > > geek@liv-inspiron:~/Build/Devel/lyx$ which moc > > /home/geek/anaconda3/bin/moc > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > > moc 5.6.0 > > > > If I'm not wrong, 'anaconda3' has something to do with the Python > install. > > And I most definitely don't have Qt 5.6.0 installed via Synaptic. > > > > As root however I get something else: > > root@liv-inspiron:/tmp# which moc > > /usr/bin/moc > > root@liv-inspiron:/tmp# moc -v > > moc 5.2.1 > > > > Is it possible that the recent Python packages I had installed have > somehow > > screwed my Qt setup? > > No, the problem you experiment is that you are using different PATH > settings when you configure and later when you issue make. The > configuration process looks for qtchooser and for a moc binary in the > PATH, and only tries this moc binary if it is in the same directory as > qtchooser. Otherwise either moc-qt4 or moc-qt5 are tried. > Unfortunately, due to limitations of the AC_CHECK_PROGS macro, the > the binaries are to be checked without their path, which is dropped. > This means that, when you configure, the ~/anaconda3/bin is not in the > PATH, so that the correct moc is spotted. But later, when you issue > "make", the ~/anaconda3/bin is in the PATH and the wrong moc is used. > You have to make sure that the PATH setting you use is the same for > both configure and make. > > Nicely spotted. I run ./configure from emelFM2, and make from bash (as it's easier to kill the process if needed). Now the Anaconda install put this in ~/.bashrc: geek@liv-inspiron:~/Build/Devel/lyx$ cat ~/.bashrc | grep -i anaconda # added by Anaconda3 4.2.0 installer export PATH="/home/geek/anaconda3/bin:$PATH" Which explains the discrepancies. Sorry all for the noise. Now the compilation advances much more nicely (though I still have `make distclean` issues, and I'll start a new thread if this issue persists). Thanks all, Liviu > -- > Enrico >
Re: master GIT broken?
On Tue, Feb 28, 2017 at 4:11 PM, Kornel Benkowrote: > Am Dienstag, 28. Februar 2017 um 15:29:37, schrieb Liviu Andronic < > landr...@lyx.org> > > On Tue, Feb 28, 2017 at 3:20 PM, Kornel Benko wrote: > > > > ... > > > > > > > Maybe the PATH env is not OK, or you have an alias for moc? > > > # which moc > > > /usr/bin/moc > > > # moc -v > > > Qt Meta Object Compiler version 63 (Qt 4.8.6) > > > > > > > > This doesn't look right, as user: > > > > geek@liv-inspiron:~/Build/Devel/lyx$ which moc > > /home/geek/anaconda3/bin/moc > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > > moc 5.6.0 > > > > If I'm not wrong, 'anaconda3' has something to do with the Python > install. > > And I most definitely don't have Qt 5.6.0 installed via Synaptic. > > > > As root however I get something else: > > root@liv-inspiron:/tmp# which moc > > /usr/bin/moc > > root@liv-inspiron:/tmp# moc -v > > moc 5.2.1 > > > > Is it possible that the recent Python packages I had installed have > somehow > > screwed my Qt setup? > > Remove /home/geek/anaconda3/bin from your PATH while configuring and > compiling for QT4. > Apparently root has PATH set without anaconda3. > > Yes, I've just noticed this as well. geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i anacon PATH=/home/geek/anaconda3/bin:/home/geek/Build/Testing/ coverity/cov-analysis-linux64-7.6.0/bin:/usr/local/sbin:/ usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games It seems this was set when I installed Anaconda (for whatever reason). I'll remove this and try again. Liviu > > Thanks, > > Liviu > > > > > > > Kornel
Re: master GIT broken?
On Tue, Feb 28, 2017 at 03:29:37PM +0100, Liviu Andronic wrote: > This doesn't look right, as user: > > geek@liv-inspiron:~/Build/Devel/lyx$ which moc > /home/geek/anaconda3/bin/moc > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > moc 5.6.0 > > If I'm not wrong, 'anaconda3' has something to do with the Python install. > And I most definitely don't have Qt 5.6.0 installed via Synaptic. > > As root however I get something else: > root@liv-inspiron:/tmp# which moc > /usr/bin/moc > root@liv-inspiron:/tmp# moc -v > moc 5.2.1 > > Is it possible that the recent Python packages I had installed have somehow > screwed my Qt setup? No, the problem you experiment is that you are using different PATH settings when you configure and later when you issue make. The configuration process looks for qtchooser and for a moc binary in the PATH, and only tries this moc binary if it is in the same directory as qtchooser. Otherwise either moc-qt4 or moc-qt5 are tried. Unfortunately, due to limitations of the AC_CHECK_PROGS macro, the the binaries are to be checked without their path, which is dropped. This means that, when you configure, the ~/anaconda3/bin is not in the PATH, so that the correct moc is spotted. But later, when you issue "make", the ~/anaconda3/bin is in the PATH and the wrong moc is used. You have to make sure that the PATH setting you use is the same for both configure and make. -- Enrico
Re: master GIT broken?
Am Dienstag, 28. Februar 2017 um 15:29:37, schrieb Liviu Andronic> On Tue, Feb 28, 2017 at 3:20 PM, Kornel Benko wrote: > ... > > > > Maybe the PATH env is not OK, or you have an alias for moc? > > # which moc > > /usr/bin/moc > > # moc -v > > Qt Meta Object Compiler version 63 (Qt 4.8.6) > > > > > This doesn't look right, as user: > > geek@liv-inspiron:~/Build/Devel/lyx$ which moc > /home/geek/anaconda3/bin/moc > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > moc 5.6.0 > > If I'm not wrong, 'anaconda3' has something to do with the Python install. > And I most definitely don't have Qt 5.6.0 installed via Synaptic. > > As root however I get something else: > root@liv-inspiron:/tmp# which moc > /usr/bin/moc > root@liv-inspiron:/tmp# moc -v > moc 5.2.1 > > Is it possible that the recent Python packages I had installed have somehow > screwed my Qt setup? Remove /home/geek/anaconda3/bin from your PATH while configuring and compiling for QT4. Apparently root has PATH set without anaconda3. > Thanks, > Liviu > > > Kornel signature.asc Description: This is a digitally signed message part.
Re: master GIT broken?
Am Dienstag, 28. Februar 2017 um 15:37:16, schrieb Liviu Andronic> On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benko wrote: > > > Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic < > > landr...@lyx.org> > > > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes < > > lasgout...@lyx.org> > > > wrote: > > > > > > > Le 28/02/2017 à 14:45, Liviu Andronic a écrit : > > > > > > > >> Not sure how to proceed next. > > > >> > > > > > > > > A few questions: > > > > > > > > - do you have only one moc binary? > > > > > > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc* > > > lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser > > > lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 -> > > > ../lib/x86_64-linux-gnu/qt4/bin/moc > > > > > > > > > > - do you have qt4 and qt5 in parallel ? > > > > > > > > > > Yes. Qt 4.8.6 and 5.2.1. > > > > > > > > > > > > > - what are the options that moc accepts? > > > > > > > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > > > moc 5.6.0 > > > > That's it. > > > > I have also both installed, but can switch in between with > > setting the environment QT_SELECT > > # setenv QT_SELECT qt5 > > # moc -v > > moc 5.2.1 > > > > > Hmm, I don't have `setenv` here. Which package did you install to get it? > That is tcsh syntax. For 'sh' it simply is 'export QT_SELECT=qt5' > Liviu Kornel signature.asc Description: This is a digitally signed message part.
Re: master GIT broken?
On Tue, Feb 28, 2017 at 3:48 PM, Liviu Andronicwrote: > > > On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benko wrote: > >> Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic < >> landr...@lyx.org> >> > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes < >> lasgout...@lyx.org> >> > > > > >> > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v >> > moc 5.6.0 >> >> That's it. >> >> I have also both installed, but can switch in between with >> setting the environment QT_SELECT >> # setenv QT_SELECT qt5 >> # moc -v >> moc 5.2.1 >> >> > For some reason this doesn't seem to have an effect here: > > geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4 > geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_sel > QT_SELECT=qt4 > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > moc 5.6.0 > > So this won't work for user, it will work for root: root@liv-inspiron:/tmp# export QT_SELECT=qt4 root@liv-inspiron:/tmp# env | grep -i qt_sel QT_SELECT=qt4 root@liv-inspiron:/tmp# moc -v Qt Meta Object Compiler version 63 (Qt 4.8.6) root@liv-inspiron:/tmp# export QT_SELECT=qt5 root@liv-inspiron:/tmp# moc -v moc 5.2.1 I'm stumped. Liviu > Liviu > > >> Kornel > > >
Re: master GIT broken?
On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benkowrote: > Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic < > landr...@lyx.org> > > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes < > lasgout...@lyx.org> > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > > moc 5.6.0 > > That's it. > > I have also both installed, but can switch in between with > setting the environment QT_SELECT > # setenv QT_SELECT qt5 > # moc -v > moc 5.2.1 > > For some reason this doesn't seem to have an effect here: geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4 geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_sel QT_SELECT=qt4 geek@liv-inspiron:~/Build/Devel/lyx$ moc -v moc 5.6.0 Liviu > Kornel
Re: master GIT broken?
On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benkowrote: > Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic < > landr...@lyx.org> > > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes < > lasgout...@lyx.org> > > wrote: > > > > > Le 28/02/2017 à 14:45, Liviu Andronic a écrit : > > > > > >> Not sure how to proceed next. > > >> > > > > > > A few questions: > > > > > > - do you have only one moc binary? > > > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc* > > lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser > > lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 -> > > ../lib/x86_64-linux-gnu/qt4/bin/moc > > > > > > > - do you have qt4 and qt5 in parallel ? > > > > > > > Yes. Qt 4.8.6 and 5.2.1. > > > > > > > > > - what are the options that moc accepts? > > > > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > > moc 5.6.0 > > That's it. > > I have also both installed, but can switch in between with > setting the environment QT_SELECT > # setenv QT_SELECT qt5 > # moc -v > moc 5.2.1 > > Hmm, I don't have `setenv` here. Which package did you install to get it? Liviu > Kornel
Re: master GIT broken?
Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic> On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes > wrote: > > > Le 28/02/2017 à 14:45, Liviu Andronic a écrit : > > > >> Not sure how to proceed next. > >> > > > > A few questions: > > > > - do you have only one moc binary? > > > > geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc* > lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser > lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 -> > ../lib/x86_64-linux-gnu/qt4/bin/moc > > > > - do you have qt4 and qt5 in parallel ? > > > > Yes. Qt 4.8.6 and 5.2.1. > > > > > - what are the options that moc accepts? > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v > moc 5.6.0 That's it. I have also both installed, but can switch in between with setting the environment QT_SELECT # setenv QT_SELECT qt5 # moc -v moc 5.2.1 Kornel signature.asc Description: This is a digitally signed message part.
Re: master GIT broken?
On Tue, Feb 28, 2017 at 3:20 PM, Kornel Benkowrote: > Am Dienstag, 28. Februar 2017 um 14:45:06, schrieb Liviu Andronic < > landr...@lyx.org> > > On Tue, Feb 28, 2017 at 1:39 PM, Kornel Benko wrote: > > > > > Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic < > > > landr...@lyx.org> > > ... > > > Still no luck. > > > > geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4 > > geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_se > > QT_SELECT=qt4 > > geek@liv-inspiron:~/Build/Devel/lyx$ make > > [...] > > Making all in src > > make[2]: Entering directory `/home/geek/Build/Devel/lyx/src' > > rm -f hash-temp \ > > @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1 > > --pretty=format:%H 2>/dev/null || echo none` ; \ > > sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp > ; \ > > cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \ > > rm -f hash-temp > > GEN moc_Compare.cpp > > Unknown options: q, t, =, q, t, 4. > > make[2]: *** [moc_Compare.cpp] Error 1 > > make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/home/geek/Build/Devel/lyx' > > make: *** [all] Error 2 > > I am out of suggestions. > I retried on clean build tree without any error. > # cd > # /configure --bindir=/usr/local/bin > --datarootdir=/usr/local/share/lyx2.3 --with-version-suffix=2.3 > # make > > Maybe the PATH env is not OK, or you have an alias for moc? > # which moc > /usr/bin/moc > # moc -v > Qt Meta Object Compiler version 63 (Qt 4.8.6) > > This doesn't look right, as user: geek@liv-inspiron:~/Build/Devel/lyx$ which moc /home/geek/anaconda3/bin/moc geek@liv-inspiron:~/Build/Devel/lyx$ moc -v moc 5.6.0 If I'm not wrong, 'anaconda3' has something to do with the Python install. And I most definitely don't have Qt 5.6.0 installed via Synaptic. As root however I get something else: root@liv-inspiron:/tmp# which moc /usr/bin/moc root@liv-inspiron:/tmp# moc -v moc 5.2.1 Is it possible that the recent Python packages I had installed have somehow screwed my Qt setup? Thanks, Liviu > Kornel
Re: master GIT broken?
Am Dienstag, 28. Februar 2017 um 14:45:06, schrieb Liviu Andronic> On Tue, Feb 28, 2017 at 1:39 PM, Kornel Benko wrote: > > > Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic < > > landr...@lyx.org> ... > Still no luck. > > geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4 > geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_se > QT_SELECT=qt4 > geek@liv-inspiron:~/Build/Devel/lyx$ make > [...] > Making all in src > make[2]: Entering directory `/home/geek/Build/Devel/lyx/src' > rm -f hash-temp \ > @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1 > --pretty=format:%H 2>/dev/null || echo none` ; \ > sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \ > cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \ > rm -f hash-temp > GEN moc_Compare.cpp > Unknown options: q, t, =, q, t, 4. > make[2]: *** [moc_Compare.cpp] Error 1 > make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/geek/Build/Devel/lyx' > make: *** [all] Error 2 I am out of suggestions. I retried on clean build tree without any error. # cd # /configure --bindir=/usr/local/bin --datarootdir=/usr/local/share/lyx2.3 --with-version-suffix=2.3 # make Maybe the PATH env is not OK, or you have an alias for moc? # which moc /usr/bin/moc # moc -v Qt Meta Object Compiler version 63 (Qt 4.8.6) Kornel signature.asc Description: This is a digitally signed message part.
Re: master GIT broken?
On Tue, Feb 28, 2017 at 12:16 PM, Liviu Andronicwrote: > I have troubles compiling current GIT. Today I've updated from e7654d9 -> > a1faa41, and all of a sudden master no longer compiles. Before the > compilation failures I did a `make distclean` which worked fine. I'm using > libqt4-dev 4.8.5 on Ubuntu 14.04. > Also, I've done a git bisect, and I couldn't find any commit that I could compile, i.e. I can't even compile e7654d9. Which points to something being wrong on my system. Liviu
Re: master GIT broken?
On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgoutteswrote: > Le 28/02/2017 à 14:45, Liviu Andronic a écrit : > >> Not sure how to proceed next. >> > > A few questions: > > - do you have only one moc binary? > geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc* lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 -> ../lib/x86_64-linux-gnu/qt4/bin/moc > - do you have qt4 and qt5 in parallel ? > Yes. Qt 4.8.6 and 5.2.1. > - what are the options that moc accepts? > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v moc 5.6.0 geek@liv-inspiron:~/Build/Devel/lyx$ moc --help Usage: moc [options] [header-file] [@option-file] Qt Meta Object Compiler version 67 (Qt 5.6.0) Options: -h, --help Displays this help. -v, --version Displays version information. -o Write output to file rather than stdout. -I Add dir to the include path for header files. -F Add Mac framework to the include path for header files. -E Preprocess only; do not generate meta object code. -D Define macro, with optional definition. -U Undefine macro. -M
Re: master GIT broken?
Le 28/02/2017 à 14:45, Liviu Andronic a écrit : Not sure how to proceed next. A few questions: - do you have only one moc binary? - do you have qt4 and qt5 in parallel ? - what are the options that moc accepts? JMarc
Re: master GIT broken?
On Tue, Feb 28, 2017 at 1:39 PM, Kornel Benkowrote: > Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic < > landr...@lyx.org> > > On Tue, Feb 28, 2017 at 1:07 PM, Kornel Benko wrote: > > > > > Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic < > > > landr...@lyx.org> > > > > On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes < > > > lasgout...@lyx.org> > > > > wrote: > > > > > > > > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit : > > > > > > > > > >> Dear all, > > > > >> I have troubles compiling current GIT. Today I've updated from > e7654d9 > > > > >> -> a1faa41, and all of a sudden master no longer compiles. Before > the > > > > >> compilation failures I did a `make distclean` which worked fine. > I'm > > > > >> using libqt4-dev 4.8.5 on Ubuntu 14.04. > > ... > > > And I'm still getting the same compilation failure: > > Making all in src > > make[2]: Entering directory `/home/geek/Build/Devel/lyx/src' > > rm -f hash-temp \ > > @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1 > > --pretty=format:%H 2>/dev/null || echo none` ; \ > > sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp > ; \ > > cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \ > > rm -f hash-temp > > GEN moc_Compare.cpp > > Unknown options: q, t, =, q, t, 4. > > make[2]: *** [moc_Compare.cpp] Error 1 > > make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/home/geek/Build/Devel/lyx' > > make: *** [all] Error 2 > > > > I am using also 'export QT_SELECT=qt4" before compiling. > > Still no luck. geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4 geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_se QT_SELECT=qt4 geek@liv-inspiron:~/Build/Devel/lyx$ make [...] Making all in src make[2]: Entering directory `/home/geek/Build/Devel/lyx/src' rm -f hash-temp \ @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1 --pretty=format:%H 2>/dev/null || echo none` ; \ sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \ cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \ rm -f hash-temp GEN moc_Compare.cpp Unknown options: q, t, =, q, t, 4. make[2]: *** [moc_Compare.cpp] Error 1 make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/geek/Build/Devel/lyx' make: *** [all] Error 2 > > And if I'm using JMarc's suggestion, I'm still getting the same error as > > before: > I also tried supplying `moc-qt4` and the compilation gets farther, but still fails: geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc-qt4 [...] Making all in frontends make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/frontends' Making all in qt4 make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/frontends/qt4' GEN ui_AboutUi.h Unknown option 'qt'. make[5]: *** [ui_AboutUi.h] Error 1 make[5]: Leaving directory `/home/geek/Build/Devel/lyx/src/frontends/qt4' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/geek/Build/Devel/lyx/src/frontends' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/geek/Build/Devel/lyx/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/geek/Build/Devel/lyx' make: *** [all] Error 2 Not sure how to proceed next. Liviu > > ... > > > > Yes, but I think that it is only because of previous compilation with > qt5. > > > > > > > > I can't be sure, but I don't think I ever compiled with Qt5 in this tree. > > What's more, before updating GIT I did a full `make distclean` which > > completed successfully, so the tree should be clean as far as past > > compilations are concerned. > > > > Liviu > > > > Kornel
Re: master GIT broken?
Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic> On Tue, Feb 28, 2017 at 1:07 PM, Kornel Benko wrote: > > > Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic < > > landr...@lyx.org> > > > On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes < > > lasgout...@lyx.org> > > > wrote: > > > > > > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit : > > > > > > > >> Dear all, > > > >> I have troubles compiling current GIT. Today I've updated from e7654d9 > > > >> -> a1faa41, and all of a sudden master no longer compiles. Before the > > > >> compilation failures I did a `make distclean` which worked fine. I'm > > > >> using libqt4-dev 4.8.5 on Ubuntu 14.04. ... > And I'm still getting the same compilation failure: > Making all in src > make[2]: Entering directory `/home/geek/Build/Devel/lyx/src' > rm -f hash-temp \ > @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1 > --pretty=format:%H 2>/dev/null || echo none` ; \ > sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \ > cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \ > rm -f hash-temp > GEN moc_Compare.cpp > Unknown options: q, t, =, q, t, 4. > make[2]: *** [moc_Compare.cpp] Error 1 > make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/geek/Build/Devel/lyx' > make: *** [all] Error 2 > I am using also 'export QT_SELECT=qt4" before compiling. > And if I'm using JMarc's suggestion, I'm still getting the same error as > before: ... > > Yes, but I think that it is only because of previous compilation with qt5. > > > > > I can't be sure, but I don't think I ever compiled with Qt5 in this tree. > What's more, before updating GIT I did a full `make distclean` which > completed successfully, so the tree should be clean as far as past > compilations are concerned. > > Liviu > Kornel signature.asc Description: This is a digitally signed message part.
Re: master GIT broken?
On Tue, Feb 28, 2017 at 1:07 PM, Kornel Benkowrote: > Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic < > landr...@lyx.org> > > On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes < > lasgout...@lyx.org> > > wrote: > > > > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit : > > > > > >> Dear all, > > >> I have troubles compiling current GIT. Today I've updated from e7654d9 > > >> -> a1faa41, and all of a sudden master no longer compiles. Before the > > >> compilation failures I did a `make distclean` which worked fine. I'm > > >> using libqt4-dev 4.8.5 on Ubuntu 14.04. > > >> > > > > > > Dear Liviu, > > > > > > What can you tell us about your 'moc' binary? What version of Qt is it > > > from? > > > It seems that it does not understand the '-qt=qt4' argument. > > > > > > > > I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Previously compilations > worked > > fine, and I hadn't changed Qt version since. > > > > So do I. > > > > > > Do you have qtchooser installed? What does 'qtchooser -l' return? > > > > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ qtchooser -l > > 4 > > 5 > > default > > qt4-i386-linux-gnu > > qt4-x86_64-linux-gnu > > qt4 > > qt5-x86_64-linux-gnu > > qt5 > > > > > > > Note that on my ancient ubuntu 12.04, I have > > > QT_MOC=moc-qt4 > > > > > > As a workaround for now, you can probably configure with QT_MOC=moc, > or at > > > least pass this to make. > > > > > > > > Still getting an error, but a later one: > > geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc > > [...] > > GEN moc_Compare.cpp > > GEN moc_PreviewLoader.cpp > > make all-recursive > > make[3]: Entering directory `/home/geek/Build/Devel/lyx/src' > > Making all in support > > make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support' > > moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h > > moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h > > make all-am > > make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support' > > CXX FileMonitor.o > > CXX ConsoleApplication.o > > In file included from ConsoleApplication.cpp:51:0: > > moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was > > generated using the moc from 5.6.0. It" > > #error "This file was generated using the moc from 5.6.0. It" > > > > Which apparently means that 'make distclean' is not working. > Remove all moc_*.cpp ui_*.h > > I removed two moc_*.cpp files (and there were no ui_*.h). Then: make clean ./autogen.sh ./configure And I'm still getting the same compilation failure: Making all in src make[2]: Entering directory `/home/geek/Build/Devel/lyx/src' rm -f hash-temp \ @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1 --pretty=format:%H 2>/dev/null || echo none` ; \ sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \ cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \ rm -f hash-temp GEN moc_Compare.cpp Unknown options: q, t, =, q, t, 4. make[2]: *** [moc_Compare.cpp] Error 1 make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/geek/Build/Devel/lyx' make: *** [all] Error 2 And if I'm using JMarc's suggestion, I'm still getting the same error as before: geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc [...] GEN moc_Compare.cpp GEN moc_PreviewLoader.cpp make all-recursive make[3]: Entering directory `/home/geek/Build/Devel/lyx/src' Making all in support make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support' moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h make all-am make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support' CXX FileMonitor.o CXX ConsoleApplication.o In file included from ConsoleApplication.cpp:51:0: moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was generated using the moc from 5.6.0. It" #error "This file was generated using the moc from 5.6.0. It" ^ moc_ConsoleApplicationPrivate.cpp:16:2: error: #error "cannot be used with the include files from this version of Qt." #error "cannot be used with the include files from this version of Qt." ^ moc_ConsoleApplicationPrivate.cpp:17:2: error: #error "(The moc has changed too much.)" #error "(The moc has changed too much.)" ^ moc_ConsoleApplicationPrivate.cpp:22:5: error: ‘QByteArrayData’ does not name a type QByteArrayData data[3]; ^ moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not declared in this scope - idx * sizeof(QByteArrayData)) \ ^ moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(0, 0, 39), // "lyx::support::ConsoleApplicat..." ^ moc_ConsoleApplicationPrivate.cpp:29:5: error: ‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared in this scope ) ^ moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(0, 0, 39), //
Re: master GIT broken?
Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic> On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes > wrote: > > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit : > > > >> Dear all, > >> I have troubles compiling current GIT. Today I've updated from e7654d9 > >> -> a1faa41, and all of a sudden master no longer compiles. Before the > >> compilation failures I did a `make distclean` which worked fine. I'm > >> using libqt4-dev 4.8.5 on Ubuntu 14.04. > >> > > > > Dear Liviu, > > > > What can you tell us about your 'moc' binary? What version of Qt is it > > from? > > It seems that it does not understand the '-qt=qt4' argument. > > > > > I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Previously compilations worked > fine, and I hadn't changed Qt version since. > So do I. > > > Do you have qtchooser installed? What does 'qtchooser -l' return? > > > > > geek@liv-inspiron:~/Build/Devel/lyx$ qtchooser -l > 4 > 5 > default > qt4-i386-linux-gnu > qt4-x86_64-linux-gnu > qt4 > qt5-x86_64-linux-gnu > qt5 > > > > Note that on my ancient ubuntu 12.04, I have > > QT_MOC=moc-qt4 > > > > As a workaround for now, you can probably configure with QT_MOC=moc, or at > > least pass this to make. > > > > > Still getting an error, but a later one: > geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc > [...] > GEN moc_Compare.cpp > GEN moc_PreviewLoader.cpp > make all-recursive > make[3]: Entering directory `/home/geek/Build/Devel/lyx/src' > Making all in support > make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support' > moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h > moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h > make all-am > make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support' > CXX FileMonitor.o > CXX ConsoleApplication.o > In file included from ConsoleApplication.cpp:51:0: > moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was > generated using the moc from 5.6.0. It" > #error "This file was generated using the moc from 5.6.0. It" > Which apparently means that 'make distclean' is not working. Remove all moc_*.cpp ui_*.h ... > > Is it possible I have some mix-up between Qt4 and Qt5? Yes, but I think that it is only because of previous compilation with qt5. > Liviu > > > > > JMarc > > Kornel signature.asc Description: This is a digitally signed message part.
Re: master GIT broken?
On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgoutteswrote: > Le 28/02/2017 à 12:16, Liviu Andronic a écrit : > >> Dear all, >> I have troubles compiling current GIT. Today I've updated from e7654d9 >> -> a1faa41, and all of a sudden master no longer compiles. Before the >> compilation failures I did a `make distclean` which worked fine. I'm >> using libqt4-dev 4.8.5 on Ubuntu 14.04. >> > > Dear Liviu, > > What can you tell us about your 'moc' binary? What version of Qt is it > from? > It seems that it does not understand the '-qt=qt4' argument. > > I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Previously compilations worked fine, and I hadn't changed Qt version since. > Do you have qtchooser installed? What does 'qtchooser -l' return? > > geek@liv-inspiron:~/Build/Devel/lyx$ qtchooser -l 4 5 default qt4-i386-linux-gnu qt4-x86_64-linux-gnu qt4 qt5-x86_64-linux-gnu qt5 > Note that on my ancient ubuntu 12.04, I have > QT_MOC=moc-qt4 > > As a workaround for now, you can probably configure with QT_MOC=moc, or at > least pass this to make. > > Still getting an error, but a later one: geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc [...] GEN moc_Compare.cpp GEN moc_PreviewLoader.cpp make all-recursive make[3]: Entering directory `/home/geek/Build/Devel/lyx/src' Making all in support make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support' moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h make all-am make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support' CXX FileMonitor.o CXX ConsoleApplication.o In file included from ConsoleApplication.cpp:51:0: moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was generated using the moc from 5.6.0. It" #error "This file was generated using the moc from 5.6.0. It" ^ moc_ConsoleApplicationPrivate.cpp:16:2: error: #error "cannot be used with the include files from this version of Qt." #error "cannot be used with the include files from this version of Qt." ^ moc_ConsoleApplicationPrivate.cpp:17:2: error: #error "(The moc has changed too much.)" #error "(The moc has changed too much.)" ^ moc_ConsoleApplicationPrivate.cpp:22:5: error: ‘QByteArrayData’ does not name a type QByteArrayData data[3]; ^ moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not declared in this scope - idx * sizeof(QByteArrayData)) \ ^ moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(0, 0, 39), // "lyx::support::ConsoleApplicat..." ^ moc_ConsoleApplicationPrivate.cpp:29:5: error: ‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared in this scope ) ^ moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(0, 0, 39), // "lyx::support::ConsoleApplicat..." ^ moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not declared in this scope - idx * sizeof(QByteArrayData)) \ ^ moc_ConsoleApplicationPrivate.cpp:33:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(1, 40, 6), // "doExec" ^ moc_ConsoleApplicationPrivate.cpp:29:5: error: ‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared in this scope ) ^ moc_ConsoleApplicationPrivate.cpp:33:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(1, 40, 6), // "doExec" ^ moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not declared in this scope - idx * sizeof(QByteArrayData)) \ ^ moc_ConsoleApplicationPrivate.cpp:34:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(2, 47, 0) // "" ^ moc_ConsoleApplicationPrivate.cpp:29:5: error: ‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared in this scope ) ^ moc_ConsoleApplicationPrivate.cpp:34:1: note: in expansion of macro ‘QT_MOC_LITERAL’ QT_MOC_LITERAL(2, 47, 0) // "" ^ In file included from ConsoleApplication.cpp:51:0: moc_ConsoleApplicationPrivate.cpp:78:103: error: ‘const struct qt_meta_stringdata_lyx__support__ConsoleApplicationPrivate_t’ has no member named ‘data’ { ::staticMetaObject, qt_meta_stringdata_lyx__support__ConsoleApplicationPrivate.data, ^ moc_ConsoleApplicationPrivate.cpp:79:82: error: ‘Q_NULLPTR’ was not declared in this scope qt_meta_data_lyx__support__ConsoleApplicationPrivate, qt_static_metacall, Q_NULLPTR, Q_NULLPTR} ^ moc_ConsoleApplicationPrivate.cpp:79:93: error: ‘Q_NULLPTR’ was not declared in this scope qt_meta_data_lyx__support__ConsoleApplicationPrivate, qt_static_metacall, Q_NULLPTR, Q_NULLPTR} ^ moc_ConsoleApplicationPrivate.cpp: In member function ‘virtual const QMetaObject* lyx::support::ConsoleApplicationPrivate::metaObject() const’: moc_ConsoleApplicationPrivate.cpp:85:57: error: ‘class QObjectData’ has no member named ‘dynamicMetaObject’ return QObject::d_ptr->metaObject ? QObject::d_ptr->dynamicMetaObject() : ^ moc_ConsoleApplicationPrivate.cpp: In member function ‘virtual void*
Re: master GIT broken?
Le 28/02/2017 à 12:16, Liviu Andronic a écrit : Dear all, I have troubles compiling current GIT. Today I've updated from e7654d9 -> a1faa41, and all of a sudden master no longer compiles. Before the compilation failures I did a `make distclean` which worked fine. I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Dear Liviu, What can you tell us about your 'moc' binary? What version of Qt is it from? It seems that it does not understand the '-qt=qt4' argument. Do you have qtchooser installed? What does 'qtchooser -l' return? Note that on my ancient ubuntu 12.04, I have QT_MOC=moc-qt4 As a workaround for now, you can probably configure with QT_MOC=moc, or at least pass this to make. JMarc