Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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 Qt files, starting with preprocessor directives that
would suggest a
  header file conflict somewhere (e.g., limits.h or so Google claims).  Let
  me know if you want more details regarding this.
  - When compiled against Qt 5.3 or 5.5, upon launching LyX, I get:
   1127 jkulesza@machine[~/SRC/lyx220/build/src]> ./lyx
   This application failed to start because it could not find or load the
   Qt platform plugin "xcb".

   Reinstalling the application may fix this problem.
   Aborted (core dumped)
   - Per the above, when I run `ldd lyx` I get:
   1128 jkulesza@machine[~/SRC/lyx220/build/src]> ldd lyx
   linux-vdso.so.1 =>  (0x7ffe76bdb000)
   libhunspell-1.2.so.0 => /usr/lib64/libhunspell-1.2.so.0
   (0x2b21963e4000)
   libaspell.so.15 => /usr/lib64/libaspell.so.15 (0x2b2196626000)
   libz.so.1 => /lib64/libz.so.1 (0x2b21968e7000)
   libmagic.so.1 => /usr/lib64/libmagic.so.1 (0x2b2196afd000)
   libQt5Concurrent.so.5 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libQt5Concurrent.so.5
   (0x2b2196d1d000)
   libQt5Svg.so.5 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libQt5Svg.so.5
   (0x2b2196f23000)
   libQt5Widgets.so.5 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libQt5Widgets.so.5
   (0x2b2197177000)
   libQt5Gui.so.5 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libQt5Gui.so.5
   (0x2b21979f6000)
   libQt5Core.so.5 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libQt5Core.so.5
   (0x2b2198209000)
   libstdc++.so.6 =>
   /usr/projects/hpcsoft/toss2/common/gcc/5.3.0/lib64/libstdc++.so.6
   (0x2b219894e000)
   libm.so.6 => /lib64/libm.so.6 (0x2b2198cdd000)
   libgcc_s.so.1 =>
   /usr/projects/hpcsoft/toss2/common/gcc/5.3.0/lib64/libgcc_s.so.1
   (0x2b2198f61000)
   libc.so.6 => /lib64/libc.so.6 (0x2b2199177000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x2b219950c000)
   libdl.so.2 => /lib64/libdl.so.2 (0x2b2199729000)
   librt.so.1 => /lib64/librt.so.1 (0x2b219992e000)
   libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x2b2199b36000)
   libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0
   (0x2b2199e67000)
   libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0
   (0x2b219a0b3000)
   libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x2b219a2b7000)
   libXext.so.6 => /usr/lib64/libXext.so.6 (0x2b219a5cf000)
   libX11.so.6 => /usr/lib64/libX11.so.6 (0x2b219a7e1000)
   libicui18n.so.54 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libicui18n.so.54
   (0x2b219ab1f000)
   libicuuc.so.54 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libicuuc.so.54
   (0x2b219af8d000)
   libicudata.so.54 =>
   /path/to/vendors/qt-5.5/Tools/QtCreator/lib/qtcreator/libicudata.so.54
   (0x2b219b33b000)
   /lib64/ld-linux-x86-64.so.2 (0x2b21961c2000)
   libnvidia-tls.so.352.93 =>
   /usr/lib64/nvidia/tls/libnvidia-tls.so.352.93 (0x2b219cd66000)
   libnvidia-glcore.so.352.93 =>
   /usr/lib64/nvidia/libnvidia-glcore.so.352.93 (0x2b219cf69000)
   libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x2b219f9fe000)
   libXau.so.6 => /usr/lib64/libXau.so.6 (0x2b219fc1c000)
   - None of the libraries indicate that they cannot be found.
   Furthermore, when I pursue the path of /usr/lib64/libxcb.so.1 I can find
   it (symlinked eventually to libxcb.so.1.1.0).

Is there something else I need to add to my PATH?  Is there a flag I can
pass to configure to disable XCB or force its location to be recognized?

Thank you,

Joel

Re: LyX 2.2.0 Linux Compilation Error

[Kornel Benko]

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 path to make sure it picks
> up the right qmake (because the one in /usr/bin is qmake-qt5).
> 
> >
> > >
> > > where I do have
> > /opt/local/rh/qt5/usr/lib64/cmake/Qt5Svg/Qt5SvgConfig.cmake
> > > but cannot seem to get CMake to see it.
> >
> > Cmake should be able to find it through the correct PATH.
> >
> 
> Same result as before:
> 
> 1016 jkulesza@machine[~/SRC/lyx220/build_cmake]> echo $PATH
> /opt/local/rh/qt5/usr/lib64/qt5/bin:/opt/local/rh/qt5/usr/bin:...

Why both? What is under /opt/local/rh/qt5/usr/lib64/qt5/bin?

> 1017 jkulesza@machine[~/SRC/lyx220/build_cmake]> cmake ../.
> -- TOP_SRC_DIR = /home/jkulesza/SRC/lyx220
> -- 
> -- Building in-source
> -- 
> -- Using GCC version 5.3.0
> -- CXX11_FLAG_DETECTED = "--std=c++11"
> -- Found Qt-Version 5.6.0
> -- Function magic_file not found
> -- Function magic_open not found
> -- Function magic_load not found
> -- Function magic_close not found
> -- Function magic_error not found
> -- Could NOT find Magic (missing:  Magic_INCLUDE_DIR Magic_LIBRARY
> HAS_MAGIC_FUNCTIONS)
> -- Could NOT find ASPELL (missing:  ASPELL_LIBRARY ASPELL_INCLUDE_DIR)
> -- ASPELL not found, building without ASPELL support
> -- Could NOT find ENCHANT (missing:  ENCHANT_LIBRARY ENCHANT_INCLUDE_DIR)
> -- ENCHANT not found, building without Enchant support
> -- Could NOT find HUNSPELL (missing:  HUNSPELL_LIBRARY
> HUNSPELL_INCLUDE_DIR)
> -- HUNSPELL not found, building without Hunspell support
> -- Using std regex
> -- 
> -- - PACKAGE : lyx2.2
> -- - PACKAGE_VERSION : 2.2.0
> -- - PROGRAM_SUFFIX  : 2.2
> -- - LYX_DATE: 2016-05-23
> -- - LYX_DIR_VER : LYX_DIR_22x
> -- - LYX_USERDIR_VER : LYX_USERDIR_22x
> -- - LYX_ABS_TOP_SRCDIR  : /home/jkulesza/SRC/lyx220
> -- - LYX_ABS_INSTALLED_DATADIR   : /usr/local/lyx2.2
> -- - LYX_ABS_INSTALLED_LOCALEDIR : /usr/local/lyx2.2/locale
> -- - LYX_INSTALL_SUFFIX  : 2.2
> -- 
> CMake Warning at /usr/lib64/cmake/Qt5Core/Qt5CoreMacros.cmake:326
> (find_package):
>   Could not find a package configuration file provided by "Qt5Svg" with any
>   of the following names:

Have you tried with clean build directory?

> Qt5SvgConfig.cmake
> qt5svg-config.cmake
> 
>   Add the installation prefix of "Qt5Svg" to CMAKE_PREFIX_PATH or set
>   "Qt5Svg_DIR" to a directory containing one of the above files.  If
> "Qt5Svg"
>   provides a separate development package or SDK, be sure it has been
>   installed.
> Call Stack (most recent call first):
>   CMakeLists.txt:607 (qt5_use_modules)
>   src/frontends/qt4/CMakeLists.txt:64 (qt_use_modules)
> 
> 
> CMake Error at /usr/lib64/cmake/Qt5Core/Qt5CoreMacros.cmake:328 (message):
>   Can not use "Svg" module which has not yet been found.
> Call Stack (most recent call first):
>   CMakeLists.txt:607 (qt5_use_modules)
>   src/frontends/qt4/CMakeLists.txt:64 (qt_use_modules)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/home/jkulesza/SRC/lyx220/CMakeFiles/CMakeOutput.log".
> See also "/home/jkulesza/SRC/lyx220/CMakeFiles/CMakeError.log"

This is because of ' Could NOT find Magic'. Please install the devel package.

> Note also
> 
> 1026 jkulesza@machine[~/SRC/lyx220/build_cmake]> which qmake
> /opt/local/rh/qt5/usr/lib64/qt5/bin/qmake
> 1027 jkulesza@machine[~/SRC/lyx220/build_cmake]> qmake -query
> QT_SYSROOT:
> QT_INSTALL_PREFIX:/usr/lib64/qt5
> QT_INSTALL_ARCHDATA:/usr/lib64/qt5
> QT_INSTALL_DATA:/usr/share/qt5
> QT_INSTALL_DOCS:/usr/share/doc/qt5
> QT_INSTALL_HEADERS:/usr/include/qt5
> QT_INSTALL_LIBS:/usr/lib64
> QT_INSTALL_LIBEXECS:/usr/lib64/qt5/libexec
> QT_INSTALL_BINS:/usr/lib64/qt5/bin
> QT_INSTALL_TESTS:/usr/lib64/qt5/tests
> QT_INSTALL_PLUGINS:/usr/lib64/qt5/plugins
> QT_INSTALL_IMPORTS:/usr/lib64/qt5/imports
> QT_INSTALL_QML:/usr/lib64/qt5/qml
> QT_INSTALL_TRANSLATIONS:/usr/share/qt5/translations
> QT_INSTALL_CONFIGURATION:/etc/xdg
> QT_INSTALL_EXAMPLES:/usr/lib64/qt5/examples
> QT_INSTALL_DEMOS:/usr/lib64/qt5/examples
> QT_HOST_PREFIX:/usr/lib64/qt5
> QT_HOST_DATA:/usr/lib64/qt5
> QT_HOST_BINS:/usr/lib64/qt5/bin
> QT_HOST_LIBS:/usr/lib64
> QMAKE_SPEC:linux-g++
> QMAKE_XSPEC:linux-g++
> QMAKE_VERSION:3.0
> QT_VERSION:5.6.0

This shows apparently the wrong QT. The output should be something like
...
 QT_INSTALL_PREFIX:/opt/local/rh/qt5/usr
...

Sorry, cannot help more.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: LyX 2.2.0 Linux Compilation Error

[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 path to make sure it picks
up the right qmake (because the one in /usr/bin is qmake-qt5).

>
> >
> > where I do have
> /opt/local/rh/qt5/usr/lib64/cmake/Qt5Svg/Qt5SvgConfig.cmake
> > but cannot seem to get CMake to see it.
>
> Cmake should be able to find it through the correct PATH.
>

Same result as before:

1016 jkulesza@machine[~/SRC/lyx220/build_cmake]> echo $PATH
/opt/local/rh/qt5/usr/lib64/qt5/bin:/opt/local/rh/qt5/usr/bin:...
1017 jkulesza@machine[~/SRC/lyx220/build_cmake]> cmake ../.
-- TOP_SRC_DIR = /home/jkulesza/SRC/lyx220
-- 
-- Building in-source
-- 
-- Using GCC version 5.3.0
-- CXX11_FLAG_DETECTED = "--std=c++11"
-- Found Qt-Version 5.6.0
-- Function magic_file not found
-- Function magic_open not found
-- Function magic_load not found
-- Function magic_close not found
-- Function magic_error not found
-- Could NOT find Magic (missing:  Magic_INCLUDE_DIR Magic_LIBRARY
HAS_MAGIC_FUNCTIONS)
-- Could NOT find ASPELL (missing:  ASPELL_LIBRARY ASPELL_INCLUDE_DIR)
-- ASPELL not found, building without ASPELL support
-- Could NOT find ENCHANT (missing:  ENCHANT_LIBRARY ENCHANT_INCLUDE_DIR)
-- ENCHANT not found, building without Enchant support
-- Could NOT find HUNSPELL (missing:  HUNSPELL_LIBRARY
HUNSPELL_INCLUDE_DIR)
-- HUNSPELL not found, building without Hunspell support
-- Using std regex
-- 
-- - PACKAGE : lyx2.2
-- - PACKAGE_VERSION : 2.2.0
-- - PROGRAM_SUFFIX  : 2.2
-- - LYX_DATE: 2016-05-23
-- - LYX_DIR_VER : LYX_DIR_22x
-- - LYX_USERDIR_VER : LYX_USERDIR_22x
-- - LYX_ABS_TOP_SRCDIR  : /home/jkulesza/SRC/lyx220
-- - LYX_ABS_INSTALLED_DATADIR   : /usr/local/lyx2.2
-- - LYX_ABS_INSTALLED_LOCALEDIR : /usr/local/lyx2.2/locale
-- - LYX_INSTALL_SUFFIX  : 2.2
-- 
CMake Warning at /usr/lib64/cmake/Qt5Core/Qt5CoreMacros.cmake:326
(find_package):
  Could not find a package configuration file provided by "Qt5Svg" with any
  of the following names:

Qt5SvgConfig.cmake
qt5svg-config.cmake

  Add the installation prefix of "Qt5Svg" to CMAKE_PREFIX_PATH or set
  "Qt5Svg_DIR" to a directory containing one of the above files.  If
"Qt5Svg"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMakeLists.txt:607 (qt5_use_modules)
  src/frontends/qt4/CMakeLists.txt:64 (qt_use_modules)


CMake Error at /usr/lib64/cmake/Qt5Core/Qt5CoreMacros.cmake:328 (message):
  Can not use "Svg" module which has not yet been found.
Call Stack (most recent call first):
  CMakeLists.txt:607 (qt5_use_modules)
  src/frontends/qt4/CMakeLists.txt:64 (qt_use_modules)


-- Configuring incomplete, errors occurred!
See also "/home/jkulesza/SRC/lyx220/CMakeFiles/CMakeOutput.log".
See also "/home/jkulesza/SRC/lyx220/CMakeFiles/CMakeError.log"

Note also

1026 jkulesza@machine[~/SRC/lyx220/build_cmake]> which qmake
/opt/local/rh/qt5/usr/lib64/qt5/bin/qmake
1027 jkulesza@machine[~/SRC/lyx220/build_cmake]> qmake -query
QT_SYSROOT:
QT_INSTALL_PREFIX:/usr/lib64/qt5
QT_INSTALL_ARCHDATA:/usr/lib64/qt5
QT_INSTALL_DATA:/usr/share/qt5
QT_INSTALL_DOCS:/usr/share/doc/qt5
QT_INSTALL_HEADERS:/usr/include/qt5
QT_INSTALL_LIBS:/usr/lib64
QT_INSTALL_LIBEXECS:/usr/lib64/qt5/libexec
QT_INSTALL_BINS:/usr/lib64/qt5/bin
QT_INSTALL_TESTS:/usr/lib64/qt5/tests
QT_INSTALL_PLUGINS:/usr/lib64/qt5/plugins
QT_INSTALL_IMPORTS:/usr/lib64/qt5/imports
QT_INSTALL_QML:/usr/lib64/qt5/qml
QT_INSTALL_TRANSLATIONS:/usr/share/qt5/translations
QT_INSTALL_CONFIGURATION:/etc/xdg
QT_INSTALL_EXAMPLES:/usr/lib64/qt5/examples
QT_INSTALL_DEMOS:/usr/lib64/qt5/examples
QT_HOST_PREFIX:/usr/lib64/qt5
QT_HOST_DATA:/usr/lib64/qt5
QT_HOST_BINS:/usr/lib64/qt5/bin
QT_HOST_LIBS:/usr/lib64
QMAKE_SPEC:linux-g++
QMAKE_XSPEC:linux-g++
QMAKE_VERSION:3.0
QT_VERSION:5.6.0

Re: LyX 2.2.0 Linux Compilation Error

[Kornel Benko]

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 admins to install Qt5 and I'll give it another go
> > > > > following that (ETA unknown).  This is perhaps a good opportunity for
> > > > them
> > > > > to get the upgrade out for other interested parties...
> > > >
> > > > OK. But make sure that the devel package of QT is installed too.
> > > >
> > >
> > > That is among what I explicitly requested.
> >
> > OK.
> >
> 
> So, now the admins are causing problems.  First, they installed a stripped
> down verison of Qt5 which lacked SVG support.  When I requested it, they
> installed all of Qt5 elsewhere.  Now, I'm having path problems where CMake
> wants to use Qt5 from /usr/lib64/qt5 but the dependencies (and an
> apparently separate, second, install) are in
> /opt/local/rh/qt5/usr/lib64/qt5.

Do you also have  "/opt/local/rh/qt5/usr/bin/qmake"?
If yes, set your PATH to "/opt/local/rh/qt5/usr/bin:$PATH"
If not, search for occurrences of all 'qmake' commands.
Check each with '/qmake -query'

> How best can I force CMake to use this Qt
> path?  Setting LD_LIBRARY_PATH, a command line parameter to CMake,
> something else?  Below is what I currently see
> 
> -- TOP_SRC_DIR = /home/jkulesza/SRC/lyx220
> -- 

...

> 
> where I do have /opt/local/rh/qt5/usr/lib64/cmake/Qt5Svg/Qt5SvgConfig.cmake
> but cannot seem to get CMake to see it.

Cmake should be able to find it through the correct PATH.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: LyX 2.2.0 Linux Compilation Error

[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 admins to install Qt5 and I'll give it another go
> > > > following that (ETA unknown).  This is perhaps a good opportunity for
> > > them
> > > > to get the upgrade out for other interested parties...
> > >
> > > OK. But make sure that the devel package of QT is installed too.
> > >
> >
> > That is among what I explicitly requested.
>
> OK.
>

So, now the admins are causing problems.  First, they installed a stripped
down verison of Qt5 which lacked SVG support.  When I requested it, they
installed all of Qt5 elsewhere.  Now, I'm having path problems where CMake
wants to use Qt5 from /usr/lib64/qt5 but the dependencies (and an
apparently separate, second, install) are in
/opt/local/rh/qt5/usr/lib64/qt5.  How best can I force CMake to use this Qt
path?  Setting LD_LIBRARY_PATH, a command line parameter to CMake,
something else?  Below is what I currently see

-- TOP_SRC_DIR = /home/jkulesza/SRC/lyx220
-- 
-- Building in-source
-- 
-- Using GCC version 5.3.0
-- CXX11_FLAG_DETECTED = "--std=c++11"
-- Found Qt-Version 5.6.0
...
-- - PACKAGE : lyx2.2
-- - PACKAGE_VERSION : 2.2.0
-- - PROGRAM_SUFFIX  : 2.2
-- - LYX_DATE: 2016-05-23
-- - LYX_DIR_VER : LYX_DIR_22x
-- - LYX_USERDIR_VER : LYX_USERDIR_22x
-- - LYX_ABS_TOP_SRCDIR  : /home/jkulesza/SRC/lyx220
-- - LYX_ABS_INSTALLED_DATADIR   : /usr/local/lyx2.2
-- - LYX_ABS_INSTALLED_LOCALEDIR : /usr/local/lyx2.2/locale
-- - LYX_INSTALL_SUFFIX  : 2.2
-- 
CMake Warning at /usr/lib64/cmake/Qt5Core/Qt5CoreMacros.cmake:326
(find_package):
  Could not find a package configuration file provided by "Qt5Svg" with any
  of the following names:

Qt5SvgConfig.cmake
qt5svg-config.cmake

  Add the installation prefix of "Qt5Svg" to CMAKE_PREFIX_PATH or set
  "Qt5Svg_DIR" to a directory containing one of the above files.  If
"Qt5Svg"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMakeLists.txt:607 (qt5_use_modules)
  src/frontends/qt4/CMakeLists.txt:64 (qt_use_modules)


CMake Error at /usr/lib64/cmake/Qt5Core/Qt5CoreMacros.cmake:328 (message):
  Can not use "Svg" module which has not yet been found.
Call Stack (most recent call first):
  CMakeLists.txt:607 (qt5_use_modules)
  src/frontends/qt4/CMakeLists.txt:64 (qt_use_modules)


-- Configuring incomplete, errors occurred!

where I do have /opt/local/rh/qt5/usr/lib64/cmake/Qt5Svg/Qt5SvgConfig.cmake
but cannot seem to get CMake to see it.

Re: LyX 2.2.0 Linux Compilation Error

[Kornel Benko]

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 the cmake-list could be of some help?

Kornel

signature.asc
Description: This is a digitally signed message part.


[CMake] VS2015 and toolset v110.mbox
Description: application/mbox

Re: LyX 2.2.0 Linux Compilation Error

[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

Re: LyX 2.2.0 Linux Compilation Error

[Kornel Benko]

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 weird with respect to the install:
> 
> 1127 jkulesza@machine[~/tmp/test]> which qmake
> /opt/local/vendor/anaconda/bin/qmake
> 1128 jkulesza@machine[~/tmp/test]> qmake --version
> QMake version 2.01a
> Using Qt version 4.8.5 in /opt/anaconda1anaconda2anaconda3/lib
> 1129 jkulesza@machine[~/tmp/test]> ls /opt/anaconda1anaconda2anaconda3/lib
> ls: cannot access /opt/anaconda1anaconda2anaconda3/lib: No such file or
> directory
> 1130 jkulesza@machine[~/tmp/test]> ls
> /opt/anaconda1anaconda2anaconda3/include
> ls: cannot access /opt/anaconda1anaconda2anaconda3/include: No such file or
> directory
> 
> I'm hoping the "fresh install" I requested from them will fix these types
> of issues.
> 

Yes, definitely weird. But maybe only your PATH points to the wrong qmake.
You should ask, where the QT4 is installed. Or search your system for other 
qmake instances.

> > > I have asked the admins to install Qt5 and I'll give it another go
> > > following that (ETA unknown).  This is perhaps a good opportunity for
> > them
> > > to get the upgrade out for other interested parties...
> >
> > OK. But make sure that the devel package of QT is installed too.
> >
> 
> That is among what I explicitly requested.

OK.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: LyX 2.2.0 Linux Compilation Error

[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 weird with respect to the install:

1127 jkulesza@machine[~/tmp/test]> which qmake
/opt/local/vendor/anaconda/bin/qmake
1128 jkulesza@machine[~/tmp/test]> qmake --version
QMake version 2.01a
Using Qt version 4.8.5 in /opt/anaconda1anaconda2anaconda3/lib
1129 jkulesza@machine[~/tmp/test]> ls /opt/anaconda1anaconda2anaconda3/lib
ls: cannot access /opt/anaconda1anaconda2anaconda3/lib: No such file or
directory
1130 jkulesza@machine[~/tmp/test]> ls
/opt/anaconda1anaconda2anaconda3/include
ls: cannot access /opt/anaconda1anaconda2anaconda3/include: No such file or
directory

I'm hoping the "fresh install" I requested from them will fix these types
of issues.


> > I have asked the admins to install Qt5 and I'll give it another go
> > following that (ETA unknown).  This is perhaps a good opportunity for
> them
> > to get the upgrade out for other interested parties...
>
> OK. But make sure that the devel package of QT is installed too.
>

That is among what I explicitly requested.

Re: LyX 2.2.0 Linux Compilation Error

[Kornel Benko]

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 another directory or pass additional options?
> 
> 
> > Where is your QT installed? Which version? Cmake tries to search for QT4.
> > Have you installed also the header files?
> > To direct cmake to search for QT5 you have to use '-DLYX_USE_QT=QT5'
> > parameter.
> > Also be sure, that QT5 bin is in PATH at prominent position.
> >
> > E.g. 'which qmake' shows the correct qt5 executable. This is how cmake
> > 'finds' qt5.
> >
> 
> I can say for certain that Qt5 is not there. I don't have good answers to
> these other questions; however, I see:
> 
> 1013 jkulesza@machine[~/SRC/lyx220/build]> which qmake
> /opt/local/vendor/anaconda/bin/qmake
> 1014 jkulesza@machine[~/SRC/lyx220/build]> qmake --version
> QMake version 2.01a
> Using Qt version 4.8.5 in /opt/anaconda1anaconda2anaconda3/lib

Your QT4 is installed under  /opt/anaconda1anaconda2anaconda3.
Look for include files in  /opt/anaconda1anaconda2anaconda3/include

> I have asked the admins to install Qt5 and I'll give it another go
> following that (ETA unknown).  This is perhaps a good opportunity for them
> to get the upgrade out for other interested parties...

OK. But make sure that the devel package of QT is installed too.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: LyX 2.2.0 Linux Compilation Error

[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 another directory or pass additional options?


> Where is your QT installed? Which version? Cmake tries to search for QT4.
> Have you installed also the header files?
> To direct cmake to search for QT5 you have to use '-DLYX_USE_QT=QT5'
> parameter.
> Also be sure, that QT5 bin is in PATH at prominent position.
>
> E.g. 'which qmake' shows the correct qt5 executable. This is how cmake
> 'finds' qt5.
>

I can say for certain that Qt5 is not there. I don't have good answers to
these other questions; however, I see:

1013 jkulesza@machine[~/SRC/lyx220/build]> which qmake
/opt/local/vendor/anaconda/bin/qmake
1014 jkulesza@machine[~/SRC/lyx220/build]> qmake --version
QMake version 2.01a
Using Qt version 4.8.5 in /opt/anaconda1anaconda2anaconda3/lib

I have asked the admins to install Qt5 and I'll give it another go
following that (ETA unknown).  This is perhaps a good opportunity for them
to get the upgrade out for other interested parties...

Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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 investigation.
>
>
Still the same error as before. :-( However, I appreciate your time
considering this!

Re: LyX 2.2.0 Linux Compilation Error

[Kornel Benko]

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 jkulesza@machine[~/SRC/lyx220/build_cmake]> cmake ../.
> -- TOP_SRC_DIR = /home/jkulesza/SRC/lyx220
> -- 
> -- Building in-source
> -- 
> -- Using GCC version 5.3.0
> -- Performing Test CXX11_FLAG_DETECTED
> -- Performing Test CXX11_FLAG_DETECTED - Success
> -- CXX11_FLAG_DETECTED = "--std=c++11"
> Warning: QT_QMAKE_EXECUTABLE reported QT_INSTALL_LIBS as
> /opt/anaconda1anaconda2anaconda3/lib
> Warning: /opt/anaconda1anaconda2anaconda3/lib does NOT exist, Qt must NOT
> be installed correctly.
> CMake Error at development/cmake/modules/FindQt4.cmake:363 (message):
>   Could NOT find QtGlobal header

Where is your QT installed? Which version? Cmake tries to search for QT4.
Have you installed also the header files?
To direct cmake to search for QT5 you have to use '-DLYX_USE_QT=QT5' parameter.
Also be sure, that QT5 bin is in PATH at prominent position.

E.g. 'which qmake' shows the correct qt5 executable. This is how cmake 'finds' 
qt5.

> Call Stack (most recent call first):
>   CMakeLists.txt:625 (find_package)
> 
> Thus, it looks like the "finder" for Qt is broken and is identifying
> something associated with my Python installation.

No, it searches for QT4, but QT4 is not installed as a devel package.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: LyX 2.2.0 Linux Compilation Error

[Georg Baum]

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 = /home/jkulesza/SRC/lyx220
> -- Building in-source
> --
> -- Using GCC version 5.3.0
> -- Performing Test CXX11_FLAG_DETECTED
> -- Performing Test CXX11_FLAG_DETECTED - Success
> -- CXX11_FLAG_DETECTED = "--std=c++11"
> Warning: QT_QMAKE_EXECUTABLE reported QT_INSTALL_LIBS as
> /opt/anaconda1anaconda2anaconda3/lib
> Warning: /opt/anaconda1anaconda2anaconda3/lib does NOT exist, Qt must NOT
> be installed correctly.
> CMake Error at development/cmake/modules/FindQt4.cmake:363 (message):
>   Could NOT find QtGlobal header
> Call Stack (most recent call first):
>   CMakeLists.txt:625 (find_package)
> 
> Thus, it looks like the "finder" for Qt is broken and is identifying
> something associated with my Python installation.

As I learned recently cmake may need QT_QMAKE_EXECUTABLE to point to the 
absolute path of the correct qmake. Since the compiler flags look mostly OK 
I would not expect that cmake would change anything here.

> Thus, it looks like I continue to be a troublemaker with respect to Qt 
(but
> now, at least, on Linux)... At this point, I'm disinclined to pursue
> additional troubleshooting for my own sake (I'm due to get a machine soon
> that I will have the ability to install a binary on); however, if this 
line
> of discussion is useful to the developers, I'm happy to pursue it.  Please
> let me know what, if anything, else I can provide that might be of use.

Sounds reasonable. Since it will be easy I'd only like to see the results of 
one additional test (see below).

> depbase=`echo sgml.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> g++ -DHAVE_CONFIG_H -I. -I../../src -I..  -I../../src
> -I../../3rdparty/boost   -DQT_NO_STL -DQT_NO_KEYWORDS -DQT_SHARED
> -I/usr/include/QtCore-std=c++11 -O2 -Wno-deprecated-declarations  -MT
> sgml.o -MD -MP -MF $depbase.Tpo -c -o sgml.o ../../src/sgml.cpp &&\
> mv -f $depbase.Tpo $depbase.Po

-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 investigation.


Georg

Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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).
>
>
> Your assumption is correct (I just run with what "configure" comes up
> with).  When I get into the office tomorrow, I'll add this flag and will
> post what I see.  That said, I do have CMake available; perhaps giving that
> a shot would be good as well - I'll try that too.  Thanks for you help to
> track this down.
>
>
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 = /home/jkulesza/SRC/lyx220
-- 
-- Building in-source
-- 
-- Using GCC version 5.3.0
-- Performing Test CXX11_FLAG_DETECTED
-- Performing Test CXX11_FLAG_DETECTED - Success
-- CXX11_FLAG_DETECTED = "--std=c++11"
Warning: QT_QMAKE_EXECUTABLE reported QT_INSTALL_LIBS as
/opt/anaconda1anaconda2anaconda3/lib
Warning: /opt/anaconda1anaconda2anaconda3/lib does NOT exist, Qt must NOT
be installed correctly.
CMake Error at development/cmake/modules/FindQt4.cmake:363 (message):
  Could NOT find QtGlobal header
Call Stack (most recent call first):
  CMakeLists.txt:625 (find_package)

Thus, it looks like the "finder" for Qt is broken and is identifying
something associated with my Python installation.

Thus, it looks like I continue to be a troublemaker with respect to Qt (but
now, at least, on Linux)... At this point, I'm disinclined to pursue
additional troubleshooting for my own sake (I'm due to get a machine soon
that I will have the ability to install a binary on); however, if this line
of discussion is useful to the developers, I'm happy to pursue it.  Please
let me know what, if anything, else I can provide that might be of use.

Thank you,
Joel

depbase=`echo sgml.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H -I. -I../../src -I..  -I../../src
-I../../3rdparty/boost   -DQT_NO_STL -DQT_NO_KEYWORDS -DQT_SHARED
-I/usr/include/QtCore-std=c++11 -O2 -Wno-deprecated-declarations  -MT
sgml.o -MD -MP -MF $depbase.Tpo -c -o sgml.o ../../src/sgml.cpp &&\
mv -f $depbase.Tpo $depbase.Po
In file included from /usr/include/QtCore/QThreadStorage:1:0,
 from ../../src/sgml.cpp:31:
/usr/include/QtCore/qthreadstorage.h: In instantiation of ‘static void
QThreadStorage::deleteData(void*) [with T =
std::map]’:
/usr/include/QtCore/qthreadstorage.h:136:43:   required from
‘QThreadStorage::QThreadStorage() [with T =
std::map]’
../../src/sgml.cpp:140:36:   required from here
/usr/include/QtCore/qthreadstorage.h:133:7: error: no matching function for
call to ‘std::map::map(void*&)’
 { delete static_cast(x); }
   ^
In file included from
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/map:61:0,
 from ../../src/Buffer.h:21,
 from ../../src/sgml.cpp:16:
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/bits/stl_map.h:273:9:
note: candidate: template std::map<_Key, _Tp,
_Compare, _Alloc>::map(_InputIterator, _InputIterator, const _Compare&,
const allocator_type&)
 map(_InputIterator __first, _InputIterator __last,
 ^
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/bits/stl_map.h:273:9:
note:   template argument deduction/substitution failed:
In file included from /usr/include/QtCore/QThreadStorage:1:0,
 from ../../src/sgml.cpp:31:
/usr/include/QtCore/qthreadstorage.h:133:7: note:   candidate expects 4
arguments, 1 provided
 { delete static_cast(x); }
   ^
In file included from
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/map:61:0,
 from ../../src/Buffer.h:21,
 from ../../src/sgml.cpp:16:
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/bits/stl_map.h:256:9:
note: candidate: template std::map<_Key, _Tp,
_Compare, _Alloc>::map(_InputIterator, _InputIterator)
 map(_InputIterator __first, _InputIterator __last)
 ^
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/bits/stl_map.h:256:9:
note:   template argument deduction/substitution failed:
In file included from /usr/include/QtCore/QThreadStorage:1:0,
 from ../../src/sgml.cpp:31:
/usr/include/QtCore/qthreadstorage.h:133:7: note:   candidate expects 2
arguments, 1 provided
 { delete static_cast(x); }
   ^
In file included from
/opt/local/contrib/gcc/rhel6_64/5.3.0/include/c++/5.3.0/map:61:0,
 from ../../src/Buffer.h:21,
 from ../../src/sgml.cpp:16:

Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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 "incorrect" quoting) and Reply (rather than Reply All).


> 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).


Your assumption is correct (I just run with what "configure" comes up
with).  When I get into the office tomorrow, I'll add this flag and will
post what I see.  That said, I do have CMake available; perhaps giving that
a shot would be good as well - I'll try that too.  Thanks for you help to
track this down.

Re: LyX 2.2.0 Linux Compilation Error

[Georg Baum]

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 
into sgml to try to clean this up.


The implementation of QThreadStorage::deleteData() is different in qt 
4.8: It redirects now to qThreadStorage_deleteData(). As a test I 
changed QThreadStorage::deleteData() to the qt 4.5 version:


static inline void deleteData(void *x)
{ delete static_cast(x); }

This does not change anything for me, compilation does still work with 
gcc 4.9. I do not really understand the failure you are seeing, but it 
might help if we could see the complete commandline of the compiler. 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).



Georg

Re: LyX 2.2.0 Linux Compilation Error

[Richard Heck]

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 *quick* reply!  That worked and let make proceed
>> beyond filetools.  Now, it complains:
>>
>>CXX  GuiApplication.o
>> ../../../../src/frontends/qt4/GuiApplication.cpp: In member function
>> ‘const QFont lyx::frontend::GuiApplication::typewriterSystemFont()’:
>> ../../../../src/frontends/qt4/GuiApplication.cpp:2588:21: error:
>> ‘Monospace’ is not a member of ‘QFont’
>> font.setStyleHint(QFont::Monospace);
>>   ^
>> make[6]: *** [GuiApplication.o] Error 1
>>
>> Is there another header file that might direct it to where it needs to
>> go.  Alternatively, is there some fail-safe logic that needs to be
>> introduced in case this font is there (seems unlikely, since 2.1.4
>> compiled and without having looked I'd be surprised if there were
>> different typewriter fonts used)?
>>
>>
>>
>
> Joel, try this. Richard, ok for 2.2.x?

Yes.

rh

Re: LyX 2.2.0 Linux Compilation Error

[Jean-Marc Lasgouttes]

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

[Georg Baum]

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 option)...

If the error is really caused by qt I would use one from a similar era. qt 
4.6 came out in 2009, so that means gcc 4.6.

However, the error could also be caused by the combination of the new 
std::string implementation (introduced in gcc 5.1) and qt, if that is the 
case then gcc 4.9 should work as well.



Georg

Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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.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 option)...

Re: LyX 2.2.0 Linux Compilation Error

[Guillaume Munch]

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 built against Qt 4.6.2 with
gcc/g++ 5.3.0 (or thereabouts)?



Maybe not. Thanks for trying :)

Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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.
>
> You could try changing it to QFont:TypeWriter.
>
>
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.  Has anyone successfully built against Qt 4.6.2 with
gcc/g++ 5.3.0 (or thereabouts)?


make.log
Description: Binary data

Re: LyX 2.2.0 Linux Compilation Error

[Guillaume Munch]

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 *quick* reply!  That worked and let make proceed
beyond filetools.  Now, it complains:

   CXX  GuiApplication.o
../../../../src/frontends/qt4/GuiApplication.cpp: In member function
‘const QFont lyx::frontend::GuiApplication::typewriterSystemFont()’:
../../../../src/frontends/qt4/GuiApplication.cpp:2588:21: error:
‘Monospace’ is not a member of ‘QFont’
font.setStyleHint(QFont::Monospace);
  ^
make[6]: *** [GuiApplication.o] Error 1

Is there another header file that might direct it to where it needs to
go.  Alternatively, is there some fail-safe logic that needs to be
introduced in case this font is there (seems unlikely, since 2.1.4
compiled and without having looked I'd be surprised if there were
different typewriter fonts used)?





Joel, try this. Richard, ok for 2.2.x?
diff --git a/src/frontends/qt4/GuiApplication.cpp b/src/frontends/qt4/GuiApplication.cpp
index 8b61379..2c166a4 100644
--- a/src/frontends/qt4/GuiApplication.cpp
+++ b/src/frontends/qt4/GuiApplication.cpp
@@ -2584,8 +2584,10 @@ QFont const GuiApplication::typewriterSystemFont()
 	QFont font("monospace");
 #endif
 	if (!isFixedPitch(font)) {
+#if QT_VERSION >= 0x040700
 		// try to enforce a real monospaced font
 		font.setStyleHint(QFont::Monospace);
+#endif
 		if (!isFixedPitch(font)) {
 			font.setStyleHint(QFont::TypeWriter);
 			if (!isFixedPitch(font)) font.setFamily("courier");

Re: LyX 2.2.0 Linux Compilation Error

[Stephan Witt]

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 make proceed 
>> beyond filetools.  Now, it complains:
>> 
>>  CXX  GuiApplication.o
>> ../../../../src/frontends/qt4/GuiApplication.cpp: In member function ‘const 
>> QFont lyx::frontend::GuiApplication::typewriterSystemFont()’:
>> ../../../../src/frontends/qt4/GuiApplication.cpp:2588:21: error: ‘Monospace’ 
>> is not a member of ‘QFont’
>>   font.setStyleHint(QFont::Monospace);
>> ^
>> make[6]: *** [GuiApplication.o] Error 1 
>> 
>> Is there another header file that might direct it to where it needs to go.  
>> Alternatively, is there some fail-safe logic that needs to be introduced in 
>> case this font is there (seems unlikely, since 2.1.4 compiled and without 
>> having looked I'd be surprised if there were different typewriter fonts 
>> used)?
> 
> This code is new and affects how the typewriter font is chosen. What version 
> of Qt do you have? 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. 
> 
> You could try changing it to QFont:TypeWriter.

Yes, this is bad. The offending code using QFont::Monospace should be guarded 
with an version check.
The use of QFont:TypeWriter is tried next two lines below.

Stephan

Re: LyX 2.2.0 Linux Compilation Error

[Stephan Witt]

Re: LyX 2.2.0 Linux Compilation Error

[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 make
> proceed beyond filetools.  Now, it complains:
>
>   CXX  GuiApplication.o
> ../../../../src/frontends/qt4/GuiApplication.cpp: In member function
> ‘const QFont lyx::frontend::GuiApplication::typewriterSystemFont()’:
> ../../../../src/frontends/qt4/GuiApplication.cpp:2588:21: error:
> ‘Monospace’ is not a member of ‘QFont’
>font.setStyleHint(QFont::Monospace);
>  ^
> make[6]: *** [GuiApplication.o] Error 1 
>
> Is there another header file that might direct it to where it needs to
> go.  Alternatively, is there some fail-safe logic that needs to be
> introduced in case this font is there (seems unlikely, since 2.1.4
> compiled and without having looked I'd be surprised if there were
> different typewriter fonts used)?

This code is new and affects how the typewriter font is chosen. What
version of Qt do you have? 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.

You could try changing it to QFont:TypeWriter.

Richard

Re: LyX 2.2.0 Linux Compilation Error

[Joel Kulesza]

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/GuiApplication.cpp: In member function ‘const
QFont lyx::frontend::GuiApplication::typewriterSystemFont()’:
../../../../src/frontends/qt4/GuiApplication.cpp:2588:21: error:
‘Monospace’ is not a member of ‘QFont’
   font.setStyleHint(QFont::Monospace);
 ^
make[6]: *** [GuiApplication.o] Error 1

Is there another header file that might direct it to where it needs to go.
Alternatively, is there some fail-safe logic that needs to be introduced in
case this font is there (seems unlikely, since 2.1.4 compiled and without
having looked I'd be surprised if there were different typewriter fonts
used)?

Re: LyX 2.2.0 Linux Compilation Error

[Richard Heck]

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  filetools.o
> ../../../src/support/filetools.cpp: In function ‘bool
> lyx::support::readLink(const lyx::support::FileName&,
> lyx::support::FileName&)’:
> ../../../src/support/filetools.cpp:980:18: error: ‘PATH_MAX’ was not
> declared in this scope
>   char linkbuffer[PATH_MAX + 1];
>   ^
> ../../../src/support/filetools.cpp:982:10: error: ‘linkbuffer’ was not
> declared in this scope
>   linkbuffer, sizeof(linkbuffer) - 1);
>   ^
> make[5]: *** [filetools.o] Error 1
>
> at which time the 'make' aborts
>
> Has anyone encountered this / is there a known workaround (or
> configure option) I'm not aware of?

Hmm. This code

#ifdef HAVE_DEF_PATH_MAX
char linkbuffer[PATH_MAX + 1];
ssize_t const nRead = ::readlink(encoded.c_str(),
 linkbuffer, sizeof(linkbuffer) - 1);
if (nRead <= 0)
return false;
linkbuffer[nRead] = '\0'; // terminator
#else

is specifically protected by the #ifdef, which should be telling us
whether PATH_MAX is defined in limits.h. Which it presumably is on your
system. I wonder if limits.h isn't getting pulled in for some reason.
You could try adding:

#include 

to support/filetools.cpp.

Richard