LyX 2.4 without GLIBC_2.38

If you are looking for a specific 64-bit package and you can't find it in any of the 64-bit repos, please post a request for it here
rych
Warlord
Warlord
Posts: 718
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

LyX 2.4 without GLIBC_2.38

Post#1 by rych » 16 Jun 2024, 12:31

Unfortunately, again, it's getting very hard to update most Apps because they now require a next version of GLIBC_2.38. Porteus is still on GLIBC_2.35:

Code: Select all

ldd --version
ldd (GNU libc) 2.35
For example, and this is my request, the fresh LyX 2.4. It's available on Slackware Current
https://slackware.pkgs.org/current/slac ... f.txz.html
https://slackers.it/repository/slackwar ... 64-1cf.txz

however, unlike the previous lyx-2.3.7-x86_64-1cf.xzm it now prints this:

Code: Select all

root@porteus:~# lyx
lyx: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by lyx)
lyx: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by lyx)
lyx: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by lyx)
ncmprhnsbl, I know it's a big ask and we've been over this before, but could you move Porteus to GLIBC_2.38!? If not, could you help me with the lyx-2.4.0-x86_64 to work under Porteus please?

Also, is PorteuX Current on GLIBC_2.38? Is PorteuX Stable on GLIBC_2.35?

rych
Warlord
Warlord
Posts: 718
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

LyX 2.4 without GLIBC_2.38

Post#2 by rych » 21 Aug 2024, 09:42

I'm afraid I'll have to build it myself using the https://slackbuilds.org/repository/15.0/office/lyx/ -- a SlackBuild rule to build the latest lyx (2.4.1). I've never done this before, so will study first... Suppose I'll succeed in building it. Are there tools in Porteus to turn the binaries into a module, instead of installing it into the live tree?

sbopkg gui only lists the previous version which is installed, doesn't communicate with the https://slackbuilds.org/repository/15.0/office/lyx/ doesn't find the update.

Maybe I could do it by hand, using this example: perl-tk compatible with perl [Solved] (Post by ncmprhnsbl #84218)

rych
Warlord
Warlord
Posts: 718
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

LyX 2.4 without GLIBC_2.38

Post#3 by rych » 22 Aug 2024, 11:21

OK, so I downloaded the SlackBuild and the source archive, and started

Code: Select all

root@porteus:/P/LyX# sh lyx.SlackBuild
It extracts the source under /tmp/SBo and immediately runs some checks. And here we come, the first thing missing that I don't know yet how to provide:

Code: Select all

...
...
lyx-2.4.1/lib/lyx2lyx/test_parser_tools.py
lyx-2.4.1/lib/lyx2lyx/Makefile.in
lyx-2.4.1/lib/lyx2lyx/lyx2lyx_version.py.in
lyx-2.4.1/lib/lyx2lyx/CMakeLists.txt
configure: WARNING: unrecognized options: --enable-qt5
configuring LyX version 2.4.1
checking for build type... release
checking for version suffix... 
checking whether Qt6 is requested... no
checking build system type... x86_64-slackware-linux-gnu
checking host system type... x86_64-slackware-linux-gnu
checking target system type... x86_64-slackware-linux-gnu
checking what packaging should be used... posix
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for a Python interpreter with version >= 2.7.0 or 3.5.0... python3
checking for python3... /usr/bin/python3
checking for python version... 3.9
checking for python platform... linux
checking for GNU default python prefix... ${prefix}
checking for GNU default python exec_prefix... ${exec_prefix}
checking for python script directory (pythondir)... ${PYTHON_PREFIX}/lib64/python3.9/site-packages
checking for python extension module directory (pyexecdir)... ${PYTHON_EXEC_PREFIX}/lib64/python3.9/site-packages
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking for ranlib... ranlib
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking whether the compiler is clang... no
checking for a good C++ mode... -std=c++17
checking whether STL is libstdc++... yes
checking whether STL is libstdc++ using the C++11 ABI... yes
checking for std::call_once availability... yes
checking for gcc... gcc
checking whether the compiler supports GNU Objective C... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking dependency style of gcc... (cached) gcc3
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lpsapi... no
checking for main in -lgdi32... no
checking for main in -lole32... no
checking whether to use included nod library... yes
checking whether to use included boost library... no
checking for boost library... yes
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking whether byte ordering is bigendian... no
checking whether printing callstack is possible... (cached) yes
checking whether make_unique is defined by header memory... yes
checking size of wchar_t... 4
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for iconv... yes
checking for working iconv... yes
checking for iconv declaration... 
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking whether to use included iconv library... no
checking whether to use included zlib library... no
checking for zlib.h... yes
checking for gzopen in -lz... yes
checking whether to build dv2dt and dt2dv... no
checking for magic.h... yes
checking for magic_open in -lmagic... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for QT_CORE... checking for QT_FRONTEND... checking for X... libraries , headers 
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for Qt library name... failed
configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR.
Firstly why configure: WARNING: unrecognized options: --enable-qt5

Secondly, checking for QT_CORE... checking for QT_FRONTEND... checking for X... libraries , headers, did we pass?

Lastly: configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR -- okay, so how do I provide Qt (Qt5 I hope) enough for compiling with it?

UPDATE. Activating the qt5-dev-5.15.3_20220318-x86_64-xfce-cinnamon-openbox-lxde-mate-gnome.xzm was enough, and we're cooking

Post Reply