Re: Compilation error on stable with Qt 5.4 in GuiLog.cpp

Le 18/10/2024 à 14:25, Jean-Marc Lasgouttes a écrit : Hi there, There is compilation error when compiling stable branch on ubuntu 15.10: at GuiLog::goTo, the code uses Sorry, this is actually GuiLog::contains QTextCursor QTextDocument::find(const QRegularExpression &expr, c

Compilation error on stable with Qt 5.4 in GuiLog.cpp

Hi there, There is compilation error when compiling stable branch on ubuntu 15.10: at GuiLog::goTo, the code uses QTextCursor QTextDocument::find(const QRegularExpression &expr, const QTextCursor &cursor, QTextDocument::FindFlags options = FindFlags()) const This has been introduc

Re: Compilation error with MSVC 19

Le 04/01/2021 à 17:30, Thibaut Cuvelier a écrit : On Mon, 4 Jan 2021 at 15:05, Jean-Marc Lasgouttes > wrote: I really wonder why this is not the default yet. The only sensible answer is "backward compatibility"… They still advertise pre-C++98 by default! Spook

Re: Compilation error with MSVC 19

On Mon, 4 Jan 2021 at 15:05, Jean-Marc Lasgouttes wrote: > Le 30/12/2020 à 09:01, Yuriy Skalko a écrit : > > I think the right way will be using only standard-compliant > > "__cplusplus" in sources and adding the option "/Zc:__cplusplus" for > > MSVC compiler in the build scripts so it handle __c

Re: Compilation error with MSVC 19

Le 30/12/2020 à 09:01, Yuriy Skalko a écrit : I think the right way will be using only standard-compliant "__cplusplus" in sources and adding the option "/Zc:__cplusplus" for MSVC compiler in the build scripts so it handle __cplusplus in standard-compliant way: https://docs.microsoft.com/en-u

Re: Compilation error with MSVC 19

On Wed, 30 Dec 2020 at 23:17, Kornel Benko wrote: > Am Wed, 30 Dec 2020 21:08:42 +0100 > schrieb Thibaut Cuvelier : > > > On Wed, 30 Dec 2020 at 16:06, Kornel Benko wrote: > > > > > Am Wed, 30 Dec 2020 15:17:36 +0100 > > > schrieb Thibaut Cuvelier : > > > > > > > On Wed, 30 Dec 2020 at 09:01, Yu

Re: Compilation error with MSVC 19

Am Wed, 30 Dec 2020 21:08:42 +0100 schrieb Thibaut Cuvelier : > On Wed, 30 Dec 2020 at 16:06, Kornel Benko wrote: > > > Am Wed, 30 Dec 2020 15:17:36 +0100 > > schrieb Thibaut Cuvelier : > > > > > On Wed, 30 Dec 2020 at 09:01, Yuriy Skalko > > wrote: > > > > > > > > Here is a newer version of th

Re: Compilation error with MSVC 19

On Wed, 30 Dec 2020 at 16:06, Kornel Benko wrote: > Am Wed, 30 Dec 2020 15:17:36 +0100 > schrieb Thibaut Cuvelier : > > > On Wed, 30 Dec 2020 at 09:01, Yuriy Skalko > wrote: > > > > > > Here is a newer version of the patch that does not use _HAS_CXX17, > as it > > > > should not really be relied

Re: Compilation error with MSVC 19

> I think the right way will be using only standard-compliant > "__cplusplus" in sources and adding the option "/Zc:__cplusplus" for > MSVC compiler in the build scripts so it handle __cplusplus in > standard-compliant way: > > > https://docs.microsoft.com/en-us/cpp/build/reference/zc-cplusplus?v

Re: Compilation error with MSVC 19

Am Wed, 30 Dec 2020 15:17:36 +0100 schrieb Thibaut Cuvelier : > On Wed, 30 Dec 2020 at 09:01, Yuriy Skalko wrote: > > > > Here is a newer version of the patch that does not use _HAS_CXX17, as it > > > should not really be relied upon ( > > > > > https://stackoverflow.com/questions/52379233/is-ha

Re: Compilation error with MSVC 19

On Wed, 30 Dec 2020 at 09:01, Yuriy Skalko wrote: > > Here is a newer version of the patch that does not use _HAS_CXX17, as it > > should not really be relied upon ( > > > https://stackoverflow.com/questions/52379233/is-has-cxx17-marco-usable-in-custom-project-headers-to-enable-c17-language > ).

Re: Compilation error with MSVC 19

Here is a newer version of the patch that does not use _HAS_CXX17, as it should not really be relied upon ( https://stackoverflow.com/questions/52379233/is-has-cxx17-marco-usable-in-custom-project-headers-to-enable-c17-language). I think the right way will be using only standard-compliant "__cp

Re: Compilation error with MSVC 19

On Wed, 30 Dec 2020 at 00:52, Thibaut Cuvelier wrote: > On Tue, 29 Dec 2020 at 23:50, Yuriy Skalko wrote: > >> > I just tried to recompile LyX on MSVC 19, this is the error I get: >> > >> > >> > [ 40%] Building CXX object >> > src/frontends/qt/CMakeFiles/frontend_qt.dir/GuiApplication.cpp.obj >>

Re: Compilation error with MSVC 19

On Tue, 29 Dec 2020 at 23:50, Yuriy Skalko wrote: > > I just tried to recompile LyX on MSVC 19, this is the error I get: > > > > > > [ 40%] Building CXX object > > src/frontends/qt/CMakeFiles/frontend_qt.dir/GuiApplication.cpp.obj > > GuiApplication.cpp > > D:\LyX\lyx-unstable\3rdparty\nod\nod.hp

Compilation error with MSVC 19

I just tried to recompile LyX on MSVC 19, this is the error I get: [ 40%] Building CXX object src/frontends/qt/CMakeFiles/frontend_qt.dir/GuiApplication.cpp.obj GuiApplication.cpp D:\LyX\lyx-unstable\3rdparty\nod\nod.hpp(272): error C2653: 'result_of': is not a class or namespace name D:\LyX\lyx

Compilation error with MSVC 19

Dear list, I just tried to recompile LyX on MSVC 19, this is the error I get: [ 40%] Building CXX object src/frontends/qt/CMakeFiles/frontend_qt.dir/GuiApplication.cpp.obj GuiApplication.cpp D:\LyX\lyx-unstable\3rdparty\nod\nod.hpp(272): error C2653: 'result_of': is not a class or namespace name

Re: de User Guide compilation error from Makeindex

On Mon, Aug 17, 2020 at 09:05:42AM +0200, Jürgen Spitzmüller wrote: > Am Montag, den 17.08.2020, 09:04 +0200 schrieb Jürgen Spitzmüller: > > Am Montag, den 17.08.2020, 01:50 -0400 schrieb Scott Kostyshak: > > > Here is the entry in the nlo file: > > > > > > \nomenclatureentry{a"@, "|, "!, ""{}@[{"

Re: de User Guide compilation error from Makeindex

On Mon, Aug 17, 2020 at 09:04:32AM +0200, Jürgen Spitzmüller wrote: > Am Montag, den 17.08.2020, 01:50 -0400 schrieb Scott Kostyshak: > > Here is the entry in the nlo file: > > > > \nomenclatureentry{a"@, "|, "!, ""{}@[{"@, "|, "!, ""{}}]\begingroup > > Das Anführungszeichen wird im TeX-Code mit d

Re: de User Guide compilation error from Makeindex

Am Montag, den 17.08.2020, 09:04 +0200 schrieb Jürgen Spitzmüller: > Am Montag, den 17.08.2020, 01:50 -0400 schrieb Scott Kostyshak: > > Here is the entry in the nlo file: > > > > \nomenclatureentry{a"@, "|, "!, ""{}@[{"@, "|, "!, > > ""{}}]\begingroup > > Das Anführungszeichen wird im TeX-Code mi

Re: de User Guide compilation error from Makeindex

Am Montag, den 17.08.2020, 01:50 -0400 schrieb Scott Kostyshak: > Here is the entry in the nlo file: > > \nomenclatureentry{a"@, "|, "!, ""{}@[{"@, "|, "!, ""{}}]\begingroup > Das Anführungszeichen wird im TeX-Code mit der Sequenz ' ""{}""{} ' > ausgegeben.\nomeqref {6.0}|nompageref}{120} Nomencl

Re: de User Guide compilation error from Makeindex

Am Montag, den 17.08.2020, 08:10 +0200 schrieb Jürgen Spitzmüller: > And which index processor do you use? nomencl processor, for that matter. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailma

Re: de User Guide compilation error from Makeindex

Am Montag, den 17.08.2020, 01:50 -0400 schrieb Scott Kostyshak: > Here is the entry in the nlo file: > > \nomenclatureentry{a"@, "|, "!, ""{}@[{"@, "|, "!, ""{}}]\begingroup > Das Anführungszeichen wird im TeX-Code mit der Sequenz ' ""{}""{} ' > ausgegeben.\nomeqref {6.0}|nompageref}{120} And whi

Re: de User Guide compilation error from Makeindex

On Mon, Aug 17, 2020 at 07:44:38AM +0200, Jürgen Spitzmüller wrote: > Am Montag, den 17.08.2020, 01:35 -0400 schrieb Scott Kostyshak: > > I get the following when compiling the German User Guide with > > pdflatex > > on master: > > > > !! Input index error (file = UserGuide.nlo, line = 6): > >

Re: de User Guide compilation error from Makeindex

Am Montag, den 17.08.2020, 01:35 -0400 schrieb Scott Kostyshak: > I get the following when compiling the German User Guide with > pdflatex > on master: > > !! Input index error (file = UserGuide.nlo, line = 6): > -- Extra `!' at position 11 of first argument. > done (7 entries accepted, 1

de User Guide compilation error from Makeindex

I get the following when compiling the German User Guide with pdflatex on master: !! Input index error (file = UserGuide.nlo, line = 6): -- Extra `!' at position 11 of first argument. done (7 entries accepted, 1 rejected). I think the problem was there before but on master we just report

Re: Compilation error on windows (master)

Le 18/03/2019 à 09:40, Kornel Benko a écrit : Am Sonntag, 17. März 2019 14:24:22 CET schrieb Jean-Marc Lasgouttes : Hi Kornel, The (French) error message below says that it is ambiguous whether sub.position(0) has an integer of cher const * argument. I am not sure how to fix it. JMarc How a

Re: Compilation error on windows (master)

Am Sonntag, 17. März 2019 14:24:22 CET schrieb Jean-Marc Lasgouttes : > Hi Kornel, > > The (French) error message below says that it is ambiguous whether > sub.position(0) has an integer of cher const * argument. I am not sure > how to fix it. > > JMarc How about sub.position(size_t(0))? The

Compilation error on windows (master)

Hi Kornel, The (French) error message below says that it is ambiguous whether sub.position(0) has an integer of cher const * argument. I am not sure how to fix it. JMarc Z:\Jean-Marc\lyx\src\lyxfind.cpp(1350): error C2668: 'boost::match_results::_Simple_types>>,std::allocator<_Ty>>::positio

Re: 2.3.x compilation error with -Werror

On Mon, Oct 08, 2018 at 11:33:19AM +0200, Jürgen Spitzmüller wrote: > Thanks, fixed. Compiles now without error. Thanks. Scott signature.asc Description: PGP signature

Re: 2.3.x compilation error with -Werror

Am Montag, den 08.10.2018, 01:07 -0400 schrieb Scott Kostyshak: > I get the following on current 2.3.x (e94ea46b) when compiling with > -Werror: > > /home/scott/lyxbuilds/2.3.x/repo/src/insets/InsetBibtex.cpp:883:2: > error: this ‘if’ clause does not guard... [-Werror=misleading- > indentation] >

2.3.x compilation error with -Werror

I get the following on current 2.3.x (e94ea46b) when compiling with -Werror: /home/scott/lyxbuilds/2.3.x/repo/src/insets/InsetBibtex.cpp:883:2: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] if (buffer().masterParams().documentClass().hasLaTeXLayout("chapter")) ^~

Re: 2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"

It seems that the problem was due to an unintentional change in the name of the folder. It had nothing to do with LyX. Apologies and thanks for your replies! Micha On 05.09.2018 14:25, Kornel Benko wrote: Am Mittwoch, 5. September 2018 14:04:50 CEST schrieb Micha H. Werner : currently, com

Re: 2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"

Le 05/09/2018 à 14:25, Kornel Benko a écrit : Am Mittwoch, 5. September 2018 14:04:50 CEST schrieb Micha H. Werner : currently, compilation of LyX2.3.1-1 fails on Ubuntu 18.04.1 LTS. This is the complete output of ./configure: root@dell:/local/lyx# ./configure Why do you do this as root? An

Re: 2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"

Am Mittwoch, 5. September 2018 14:04:50 CEST schrieb Micha H. Werner : > currently, compilation of LyX2.3.1-1 fails on Ubuntu 18.04.1 LTS. > > This is the complete output of ./configure: > > root@dell:/local/lyx# ./configure Why do you do this as root? And why in the source dir? > configuring

2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"

currently, compilation of LyX2.3.1-1 fails on Ubuntu 18.04.1 LTS. This is the complete output of ./configure: root@dell:/local/lyx# ./configure configuring LyX version 2.3.0 checking for build type... release checking for version suffix... checking whether Qt5 is requested... no checking build s

Re: compilation error with sk.po

El 02.01.2018 a las 13:55, Jürgen Spitzmüller escribió: Please try again. Hello Jürgen, I wish you too all the best for the new year. Many thanks for your commit, I can now compile. regards Uwe

Re: compilation error with sk.po

Am Dienstag, den 02.01.2018, 13:12 +0100 schrieb Uwe Stöhr: > D:/LyXGit/Master/compile-2015/po/encodings_l10n.pot -t encodings > --src_file=D:/LyXGit/Master/compile-2015/po/encodings_files > CUSTOMBUILD : error : Unable to handle line: > [D:\LyXGit\Master\compile-2015\po\translations.vcxproj] >

Re: compilation error with sk.po

Am Dienstag, 2. Januar 2018 um 13:12:55, schrieb Uwe Stöhr > Hi Kornel, > > I wish you and your family a happy new year. > > With JMarc's patch I can compile master again but encounter now this: > >Generating qt4_files >Generating layouts_files >Generating languages_files >Gener

compilation error with sk.po

Hi Kornel, I wish you and your family a happy new year. With JMarc's patch I can compile master again but encounter now this: Generating qt4_files Generating layouts_files Generating languages_files Generating latexfonts_files Generating encodings_files Generating ui_files Generat

Re: cmake compilation error

Am Sonntag, 12. März 2017 um 19:52:57, schrieb Guillaume Munch > Le 12/03/2017 à 16:51, Kornel Benko a écrit : > > > > Should we emit a warning (which probably will be ignored) or better refuse > > to build > > with "5.0" <= QT < "5.4" ? > > I don't think so, the indication INSTALL file should b

Re: cmake compilation error

Le 12/03/2017 à 16:51, Kornel Benko a écrit : Should we emit a warning (which probably will be ignored) or better refuse to build with "5.0" <= QT < "5.4" ? I don't think so, the indication INSTALL file should be enough in that case. From my POV, if user selects QT5, we should use it. A

Re: cmake compilation error

Am Samstag, 11. März 2017 um 22:23:22, schrieb Guillaume Munch > Le 11/03/2017 à 18:07, Jean-Pierre Chrétien a écrit : > > Le 11/03/2017 à 17:57, Kornel Benko a écrit : > > > >> I see the same with installed QT5.2.1. But no problems with QT5.7. > > > > Seems that I've got 5.3.2 here, Debian Jessie

Re: cmake compilation error

Le 11/03/2017 à 18:07, Jean-Pierre Chrétien a écrit : Le 11/03/2017 à 17:57, Kornel Benko a écrit : I see the same with installed QT5.2.1. But no problems with QT5.7. Seems that I've got 5.3.2 here, Debian Jessie (up to date stable). Indeed the function is introduced in qt5.4. It is now fix

Re: cmake compilation error

Le 11/03/2017 à 17:57, Kornel Benko a écrit : I see the same with installed QT5.2.1. But no problems with QT5.7. Seems that I've got 5.3.2 here, Debian Jessie (up to date stable). -- Jean-Pierre

Re: cmake compilation error

Am Samstag, 11. März 2017 um 17:43:54, schrieb Jean-Pierre Chrétien > Hello, > > I get this with a clean build of up-to-date master: > > /ext/lyx/master/src/support/FileMonitor.cpp: In member function ‘void > lyx::support::FileMonitorGuard::refresh(bool)’: > /ext/lyx/master/src/support/FileMon

cmake compilation error

Hello, I get this with a clean build of up-to-date master: /ext/lyx/master/src/support/FileMonitor.cpp: In member function ‘void lyx::support::FileMonitorGuard::refresh(bool)’: /ext/lyx/master/src/support/FileMonitor.cpp:115:6: error: no matching function for call to ‘QTimer::singleShot(int, l

Re: compilation error with current master

Le 07/12/2016 à 13:57, Jan Niklas Hasse a écrit : Hi, try adding #include to Encoding.cpp. Yes On Wed, 7 Dec 2016, at 00:36, Uwe Stöhr wrote: With today's master I get this compilation error: Encoding.cpp D:\LyXGit\Master\src\Encoding.cpp(267): error C3861: 'bac

Re: compilation error with current master

Hi, try adding #include to Encoding.cpp. - Jan On Wed, 7 Dec 2016, at 00:36, Uwe Stöhr wrote: > With today's master I get this compilation error: > > Encoding.cpp > D:\LyXGit\Master\src\Encoding.cpp(267): error C3861: 'back_inserter': > identifier not found

compilation error with current master

With today's master I get this compilation error: Encoding.cpp D:\LyXGit\Master\src\Encoding.cpp(267): error C3861: 'back_inserter': identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj] regards Uwe

Re: LyX 2.2.0 Linux Compilation Error

Developers: By way of update: - I was able to compile against Qt 5.3 and Qt 5.5 using configure but with neither using cmake - With both configure and cmake, my PATH and LD_LIBRARY_PATHs were identical. Cmake would begin compiling, but a series of errors would occur in the Q

Re: compilation error in branch and master

Am 02.07.2016 um 18:39 schrieb Georg Baum: Did you recompile at least once after the compiler upgrade? i tried but it was not possible due to the error. Please try again. My old code contained a thinko and did not do what I wanted it to do. Thanks, this works now. I can also compile the 2

Re: compilation error in branch and master

Uwe Stöhr wrote: > Am 02.07.2016 um 17:34 schrieb Uwe Stöhr: > >> I still get the same compilation error: > > Very, very weird: I just recompiled it without changing anything. it is > incredible but now it compile. Did you recompile at least once after the compiler upg

Re: compilation error in branch and master

Am 02.07.2016 um 17:34 schrieb Uwe Stöhr: I still get the same compilation error: Very, very weird: I just recompiled it without changing anything. it is incredible but now it compile. So I can now compile master again. I'll now try 2.2.x. Please modify your today's commit

Re: compilation error in branch and master

Am 02.07.2016 um 03:19 schrieb Uwe Stöhr: No, I created separate folders for every git branch to be able to use different CMake configs for every branch. Very good. Please send CMakeError.log There is no such file. and CMakeOutput.log This one is attached. Here we need to distinguis

Re: Do we want to keep any temporary files after a compilation error?

Scott Kostyshak wrote: > If not, it seems we can just have a fresh start when compiling again > after an error. That is, instead of using the hard-coded list, we just > remove all temporary files. +1 The temporary files can be useful for error analysis, so they should not be deleted right after

Do we want to keep any temporary files after a compilation error?

e are compiling after there was an error. I think the main question that needs an answer is: Are there any temporary files that we want to keep after a compilation error? If not, it seems we can just have a fresh start when compiling again after an error. That is, instead of using the hard-code

Re: compilation error in branch and master

Am 01.07.2016 um 05:03 schrieb Richard Heck: Something has changed in your build system. None of that code has been touched for many years. Yes, the error occurred with the latest MSVC 2015 update 3. Unfortunately I cannot go back to update 2 (MSVC doesn't offer this) and can therefore no lo

Re: compilation error in branch and master

Richard Heck wrote: > On 06/30/2016 07:36 PM, Uwe Stöhr wrote: >> compiling today's 2.2.x branch and master I get this compilation error: >> >> environment.cpp >> D:\LyXGit\Master\src\support\environment.cpp(73): fatal error C1189: >> #error: No environ

Re: compilation error in branch and master

On 06/30/2016 07:36 PM, Uwe Stöhr wrote: compiling today's 2.2.x branch and master I get this compilation error: environment.cpp D:\LyXGit\Master\src\support\environment.cpp(73): fatal error C1189: #error: No environment-setting function has been defined. [D:\LyXGit\Master\compile-201

compilation error in branch and master

compiling today's 2.2.x branch and master I get this compilation error: environment.cpp D:\LyXGit\Master\src\support\environment.cpp(73): fatal error C1189: #error: No environment-setting function has been defined. [D:\LyXGit\Master\compile-2015\src\support\support.vcxproj] regards Uwe

Re: LyX 2.2.0 Linux Compilation Error

Am Montag, 27. Juni 2016 um 12:27:02, schrieb Joel Kulesza > On Mon, Jun 27, 2016 at 11:48 AM, Kornel Benko wrote: > > > Do you also have "/opt/local/rh/qt5/usr/bin/qmake"? > > If yes, set your PATH to "/opt/local/rh/qt5/usr/bin:$PATH" > > > > Done, see below. Note that I prepended another pat

Re: LyX 2.2.0 Linux Compilation Error

On Mon, Jun 27, 2016 at 11:48 AM, Kornel Benko wrote: > Do you also have "/opt/local/rh/qt5/usr/bin/qmake"? > If yes, set your PATH to "/opt/local/rh/qt5/usr/bin:$PATH" > > Done, see below. Note that I prepended another path to make sure it picks up the right qmake (because the one in /usr/bin

Re: LyX 2.2.0 Linux Compilation Error

Am Montag, 27. Juni 2016 um 11:33:17, schrieb Joel Kulesza > On Mon, Jun 20, 2016 at 4:21 PM, Kornel Benko wrote: > > > Am Montag, 20. Juni 2016 um 16:04:03, schrieb Joel Kulesza < > > jkule...@gmail.com> > > > On Mon, Jun 20, 2016 at 3:39 PM, Kornel Benko wrote: > > > > > I have asked the admi

Re: LyX 2.2.0 Linux Compilation Error

On Mon, Jun 20, 2016 at 4:21 PM, Kornel Benko wrote: > Am Montag, 20. Juni 2016 um 16:04:03, schrieb Joel Kulesza < > jkule...@gmail.com> > > On Mon, Jun 20, 2016 at 3:39 PM, Kornel Benko wrote: > > > > I have asked the admins to install Qt5 and I'll give it another go > > > > following that (ET

Re: LyX 2.2.0 Linux Compilation Error

Am Dienstag, 21. Juni 2016 um 20:35:55, schrieb Georg Baum > Joel Kulesza wrote: > > > Still the same error as before. :-( However, I appreciate your time > > considering this! > > OK, then I have no idea anymore. Hopefully the new install will fix it. > > > Georg Maybe the attached mail from th

Re: LyX 2.2.0 Linux Compilation Error

Joel Kulesza wrote: > Still the same error as before. :-( However, I appreciate your time > considering this! OK, then I have no idea anymore. Hopefully the new install will fix it. Georg

Re: LyX 2.2.0 Linux Compilation Error

Am Montag, 20. Juni 2016 um 16:04:03, schrieb Joel Kulesza > On Mon, Jun 20, 2016 at 3:39 PM, Kornel Benko wrote: > > > > > Your QT4 is installed under /opt/anaconda1anaconda2anaconda3. > > Look for include files in /opt/anaconda1anaconda2anaconda3/include > > > > Something is definitely weir

Re: LyX 2.2.0 Linux Compilation Error

On Mon, Jun 20, 2016 at 3:39 PM, Kornel Benko wrote: > > Your QT4 is installed under /opt/anaconda1anaconda2anaconda3. > Look for include files in /opt/anaconda1anaconda2anaconda3/include > Something is definitely weird with respect to the install: 1127 jkulesza@machine[~/tmp/test]> which qma

Re: LyX 2.2.0 Linux Compilation Error

Am Montag, 20. Juni 2016 um 15:25:02, schrieb Joel Kulesza > On Mon, Jun 20, 2016 at 1:07 PM, Kornel Benko wrote: > > > > > Please give us the full command line used fir the cmake call. > > > > cmake ../. --- which points to the CMakeLists in the base directory. > Perhaps I should point it to

Re: LyX 2.2.0 Linux Compilation Error

On Mon, Jun 20, 2016 at 1:07 PM, Kornel Benko wrote: > > Please give us the full command line used fir the cmake call. > cmake ../. --- which points to the CMakeLists in the base directory. Perhaps I should point it to another directory or pass additional options? > Where is your QT installed

Re: LyX 2.2.0 Linux Compilation Error

On Mon, Jun 20, 2016 at 12:59 PM, Georg Baum wrote: > > -std=c++11 wil likely not work with the old qt. The other flags look OK. I > would be interested to see what happens if you call configure with -- > disable-cxx11. If that does not help then I am out of ideas and would > suggest to stop the

Re: LyX 2.2.0 Linux Compilation Error

Am Montag, 20. Juni 2016 um 09:03:35, schrieb Joel Kulesza > > On Sun, Jun 19, 2016 at 9:53 AM, Georg Baum < > > georg.b...@post.rwth-aachen.de> wrote: > > ... > > I did try compiling with CMake and see the error(s) below: Please give us the full command line used fir the cmake call. > 1026 j

Re: LyX 2.2.0 Linux Compilation Error

Joel Kulesza wrote: > All the gore and carnage for the failing source file from the configure > with "--disable-silent-rules" below my signature. > > I did try compiling with CMake and see the error(s) below: > > 1026 jkulesza@machine[~/SRC/lyx220/build_cmake]> cmake ../. > -- TOP_SRC_DIR = /hom

Re: LyX 2.2.0 Linux Compilation Error

On Sun, Jun 19, 2016 at 3:30 PM, Joel Kulesza wrote: > On Sun, Jun 19, 2016 at 9:53 AM, Georg Baum < > georg.b...@post.rwth-aachen.de> wrote: > > >> You get this if you call configure with --disable-silent-rules (from the >> log file I assume that you use autotools and not cmake to compile). > >

Re: LyX 2.2.0 Linux Compilation Error

On Sun, Jun 19, 2016 at 9:53 AM, Georg Baum wrote: > Sorry, I overlooked this (please post always to the list, then others can > help as well). Sorry for the oversight (again). Consistent with the separate discussion that Scott kicked off, my simple mind is too used to using Gmail (leading to

Re: LyX 2.2.0 Linux Compilation Error

Sorry, I overlooked this (please post always to the list, then others can help as well). Am 12.06.2016 um 23:47 schrieb Joel Kulesza: For the sake of complete communication: I've seen failures with 4.6.1, 4.9.2, and 5.3.0. At this point, I'm not sure of a way to proceed without a deep dive i

Re: LyX 2.2.0 Linux Compilation Error

On 06/11/2016 12:32 AM, Guillaume Munch wrote: > Le 11/06/2016 04:40, Joel Kulesza a écrit : >> On Fri, Jun 10, 2016 at 3:56 PM, Richard Heck > > wrote: >> >> You could try adding: >> >> #include >> >> to support/filetools.cpp. >> >> >> Richard, thanks for the *q

Re: LyX 2.2.0 Linux Compilation Error

Le 10/06/16 à 23:56, Richard Heck a écrit : You could try adding: #include to support/filetools.cpp. Why not use instead? I am not sure what the difference is, but using the C++ version sounds better. JMarc

Re: LyX 2.2.0 Linux Compilation Error

Joel Kulesza wrote: > I have gcc 4.6.1, 4.7.0, 4.7.2, 4.8.2, 4.9.2, and 5.3.0 available. Are > any > of those known to be particularly successful with this vintage of Qt? If > not, I'm afraid I'll be without 2.2.0 on this system (I am not the admin > so simply installing a package isn't an optio

Re: LyX 2.2.0 Linux Compilation Error

On Fri, Jun 10, 2016 at 11:40 PM, Guillaume Munch wrote: > > I don't understand, but try passing --disable-cxx11 to configure. Same error. :-( > > > Has anyone successfully built against Qt 4.6.2 with >> gcc/g++ 5.3.0 (or thereabouts)? >> >> > Maybe not. Thanks for trying :) > > I have gcc 4.6

Re: LyX 2.2.0 Linux Compilation Error

Le 11/06/2016 06:12, Joel Kulesza a écrit : This got me well beyond the monospace issue; however, more Qt woes (which now appear to be intrinsic to Qt). See attached to avoid a long copy-and-paste. I don't understand, but try passing --disable-cxx11 to configure. Has anyone successfully bui

Re: LyX 2.2.0 Linux Compilation Error

On Fri, Jun 10, 2016 at 10:13 PM, Richard Heck wrote: > This code is new and affects how the typewriter font is chosen. What > version of Qt do you have? > Qt 4.6.2. > It appears that QFont::Monospace does not exist before Qt 4.7. This is > bad, since the INSTALL file says one can use 4.5.0. >

Re: LyX 2.2.0 Linux Compilation Error

Le 11/06/2016 04:40, Joel Kulesza a écrit : On Fri, Jun 10, 2016 at 3:56 PM, Richard Heck mailto:rgh...@lyx.org>> wrote: You could try adding: #include to support/filetools.cpp. Richard, thanks for the *quick* reply! That worked and let make proceed beyond filetools. Now, it c

Re: LyX 2.2.0 Linux Compilation Error

Am 11.06.2016 um 06:13 schrieb Richard Heck : > > On 06/10/2016 11:40 PM, Joel Kulesza wrote: >> On Fri, Jun 10, 2016 at 3:56 PM, Richard Heck wrote: >> You could try adding: >> >> #include >> >> to support/filetools.cpp. >> >> >> Richard, thanks for the quick reply! That worked and let mak

Re: LyX 2.2.0 Linux Compilation Error

Re: LyX 2.2.0 Linux Compilation Error

On 06/10/2016 11:40 PM, Joel Kulesza wrote: > On Fri, Jun 10, 2016 at 3:56 PM, Richard Heck > wrote: > > You could try adding: > > #include > > to support/filetools.cpp. > > > Richard, thanks for the *quick* reply! That worked and let make > proceed beyond file

Re: LyX 2.2.0 Linux Compilation Error

On Fri, Jun 10, 2016 at 3:56 PM, Richard Heck wrote: > You could try adding: > > #include > > to support/filetools.cpp. > > Richard, thanks for the *quick* reply! That worked and let make proceed beyond filetools. Now, it complains: CXX GuiApplication.o ../../../../src/frontends/qt4/Gu

Re: LyX 2.2.0 Linux Compilation Error

On 06/10/2016 04:25 PM, Joel Kulesza wrote: > LyX Developers, > > I'm attempting to compile LyX 2.2.0 for local/single user use on RHEL6 > with GCC 5.3.0 / Python 3.4 (see below signature for configure > summary) and very quickly run into errors on make. Specifically, I see: > > CXX filetoo

LyX 2.2.0 Linux Compilation Error

LyX Developers, I'm attempting to compile LyX 2.2.0 for local/single user use on RHEL6 with GCC 5.3.0 / Python 3.4 (see below signature for configure summary) and very quickly run into errors on make. Specifically, I see: CXX filetools.o ../../../src/support/filetools.cpp: In function ‘bo

operator << compilation error

While playing around with the latest MSVC compiler that is now C++17 feature complete (MSVC 2015 update 2) I get the following compilation error error C2593: 'operator <<' is ambiguous According to https://support.microsoft.com/en-us/kb/168440 there is an easy workaround. Si

Re: compilation error with Re: We now include both png and svgz?

Am 07.12.2015 um 22:53 schrieb Kornel Benko: That is not enough, you have also remove the object files many thanks! Now the error is gone. best regards Uwe

Re: compilation error with Re: We now include both png and svgz?

Am Montag, 7. Dezember 2015 um 22:38:48, schrieb Kornel Benko > Am Montag, 7. Dezember 2015 um 22:10:35, schrieb Uwe Stöhr > > Am 07.12.2015 um 19:48 schrieb Enrico Forestieri: > > > > > Done at db363ab1. > > > > Now I get a compilation error: >

Re: compilation error with Re: We now include both png and svgz?

Am Montag, 7. Dezember 2015 um 22:10:35, schrieb Uwe Stöhr > Am 07.12.2015 um 19:48 schrieb Enrico Forestieri: > > > Done at db363ab1. > > Now I get a compilation error: > >Generating qrc_Resources.cpp >RCC: Error in > 'D:/LyXGit/Master/compile-2

compilation error with Re: We now include both png and svgz?

Am 07.12.2015 um 19:48 schrieb Enrico Forestieri: Done at db363ab1. Now I get a compilation error: Generating qrc_Resources.cpp RCC: Error in 'D:/LyXGit/Master/compile-2013/src/frontends/qt4/Resources.qrc' : Cannot find file 'D:/LyXGit/Master/lib/images/all-changes-acce

Re: Compilation error with gcc 4.6

2015-05-19 15:20 GMT+02:00 Jean-Marc Lasgouttes: > It should be found using i18nLibFileSearch(). > I see. > > The way it is done for other elements is to look for example for > doc/fr/UserGuide.lyx. This would make us create directories fr/ de/... in > the toplevel system directory, which may n

Re: Compilation error with gcc 4.6

Le 19/05/2015 12:46, Jürgen Spitzmüller a écrit : Also, are there plans to allow for a translation now that they are exposed in the UI? We could do that. How? Look for RELEASE-NOTES_fr etc. and display that if available? It should be found using i18nLibFileSearch(). The way it is don

Re: Compilation error with gcc 4.6

2015-05-19 11:05 GMT+02:00 Jean-Marc Lasgouttes: > It works perfectly with this patch, thanks. > OK. I feel stupid (passing a QList to std sort) > > Concerning the release notes, I do not find them very discoverable in the > attached screen-shot. > Should be better now. > > Also, are there p

Re: Compilation error with gcc 4.6

Le 19/05/2015 09:28, Jürgen Spitzmüller a écrit : 2015-05-18 19:52 GMT+02:00 Jürgen Spitzmüller And with this? Ping It works perfectly with this patch, thanks. Concerning the release notes, I do not find them very discoverable in the attached screen-shot. Also, are there plans to all

Re: Compilation error with gcc 4.6

2015-05-18 19:52 GMT+02:00 Jürgen Spitzmüller > And with this? > Ping Jürgen

Re: Compilation error with gcc 4.6

2015-05-18 19:29 GMT+02:00 Jürgen Spitzmüller : > 2015-05-18 19:24 GMT+02:00 Richard Heck: > >> On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: >> >>> >>> Since this week-end, I have compilation errors with gcc 4.6. I am not >>> sure from where to start to diagnose this. >>> >> >> This is the

  1   2   3   >