[SOLVED] qt5 on top of Slackware 14.2

cdek · 10-24-2016, 01:41 AM

newbie question ...

Some applications on Slackbuilds require qt5 (eg calibre) so I would like to install it just as a dependency for those applications.

I've just finished compiling it, but before I install, I would like to know whether it's safe to do so. I really don't want to mess up my precious Slackware installation.

Is there anything I need to be aware of?

montagdude · 10-24-2016, 02:01 AM

Did you build the version from SBo? If so, it's set up to ensure that nothing from qt4 is overwritten. If not, I'd recommend you have a look at the SlackBuild script from SBo to see what they did. Another option would be to use Alien Bob's qt5 package, which will also leave everything from qt4 intact, and it is already compiled for you.

gmgf · 10-24-2016, 04:22 AM

Just looked, here:

http://alien.slackbook.org/ktown/

http://alien.slackbook.org/ktown/14.2/5/x86_64/deps/

dugan · 10-24-2016, 08:44 AM

For Calibre, you can use my SlackBuild to download and package the prebuilt binaries. It includes its own Qt 5 build, so you don't need to build Qt 5 separately.

https://github.com/duganchen/my_slac...bre.SlackBuild

I do install Qt 5 for reasons other than Calibre. The Qt package I install is this one:

http://www.slackware.com/~alien/slackbuilds/qt5/

cdek · 10-25-2016, 03:36 AM

I built the version from Slackbuilds. It took an insane amount of time to build, but all went well. I installed it and everything seems to be working just fine. Thank you!

dugan · 10-25-2016, 11:58 AM

Does anyone know why both Alien Bob's Qt 5 package for slackware64-current (not the one in ktown) and SBo's build script are for 5.6? Is there a technical reason for not moving to 5.7, or is the reason just "didn't get around to updating it yet"?

a4z · 10-25-2016, 12:27 PM

Quote:

Originally Posted by dugan

Does anyone know why both Alien Bob's Qt 5 package for slackware64-current (not the one in ktown) and SBo's build script are for 5.6? Is there a technical reason for not moving to 5.7, or is the reason just "didn't get around to updating it yet"?

not sure if this is the indention, but
5.6 is LTS, 5.7 already nearly EOF, so together with LTS KDE I would use 5.6.

5.7 only for development that will be ready some when in the future, 5.8 might have new features, but those are mostly uninteresting for desktop usage.

so 5.6.x is excellent for stable desktop apps

kevmccor · 03-20-2018, 10:41 AM

I tried to build qt5 (Version 5.9.4) from AlienBob's qt5 script, but the build failed. I downloaded qt-everywhere-opensource-src-5.9.4.tar.xz from https://www1.qt.io/offline-installers/. Hopefully this extract from the build output explains the error.

Code:

main.cpp:(.text+0x3d5c): undefined reference to `QCommandLineOption::setFlags(QFlags<QCommandLineOption::Flag>)'
main.cpp:(.text+0x3dfb): undefined reference to `QCommandLineOption::setFlags(QFlags<QCommandLineOption::Flag>)'
main.cpp:(.text+0x3e9d): undefined reference to `QCommandLineOption::setFlags(QFlags<QCommandLineOption::Flag>)'
main.cpp:(.text+0x3fa8): undefined reference to `QCommandLineOption::setFlags(QFlags<QCommandLineOption::Flag>)'
main.cpp:(.text+0x404a): undefined reference to `QCommandLineOption::setFlags(QFlags<QCommandLineOption::Flag>)'
.obj/main.o:main.cpp:(.text+0x40ec): more undefined references to `QCommandLineOption::setFlags(QFlags<QCommandLineOption::Flag>)' follow
.obj/main.o: In function `runMoc(int, char**)':
main.cpp:(.text+0x7d74): undefined reference to `QtPrivate::QStringList_join(QStringList const&, QLatin1String)'
collect2: error: ld returned 1 exit status
Makefile:134: recipe for target '../../../bin/moc' failed
make[3]: *** [../../../bin/moc] Error 1
make[3]: Leaving directory '/tmp/qt-everywhere-opensource-src-5.9.4/qtbase/src/tools/moc'
Makefile:93: recipe for target 'sub-moc-make_first' failed
make[2]: *** [sub-moc-make_first] Error 2
make[2]: Leaving directory '/tmp/qt-everywhere-opensource-src-5.9.4/qtbase/src'
Makefile:48: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory '/tmp/qt-everywhere-opensource-src-5.9.4/qtbase'
Makefile:82: recipe for target 'module-qtbase-make_first' failed
make: *** [module-qtbase-make_first] Error 2

I have the version 5.7.1 from Slackbuilds (qt5-5.7.1-x86_64-1_SBo qt5-webkit-5.7.1-x86_64-1_SBo).

I am trying to install the zoom web conferencing service. It requires Qt 5.9.

Code:

$ /opt/zoom/zoom
/opt/zoom/zoom: /usr/lib64/libQt5Core.so.5: version `Qt_5.9' not found (required by /opt/zoom/zoom)

I have no idea whether other programs that use Qt5 will still work after the Qt5 is upgraded.
My purpose in all this is to be able to record audio and video from conferences. Apparently this cannot be done with skype, but since I am a newbie to this, I am casting about for a solution that I can manage.

Thanks

Alien Bob · 03-20-2018, 11:09 AM

Quote:

Originally Posted by dugan

Does anyone know why both Alien Bob's Qt 5 package for slackware64-current (not the one in ktown) and SBo's build script are for 5.6? Is there a technical reason for not moving to 5.7, or is the reason just "didn't get around to updating it yet"?

http://www.slackware.com/~alien/slac...pkg64/current/ where do you see 5.6?

chris.willing · 03-20-2018, 05:03 PM

Quote:

Originally Posted by Alien Bob

http://www.slackware.com/~alien/slac...pkg64/current/ where do you see 5.6?

The question about versions was asked 26th October 2016

kevmccor · 03-21-2018, 08:03 AM

My bad. This seemed like the most relevant thread for issues with building qt5.

Candelabrus · 03-21-2018, 06:49 PM

You can try my .slackbuild
take about 45min to compile using i5 4670k @ 4.4ghz

bassmadrigal · 03-24-2018, 01:56 AM

Quote:

Originally Posted by kevmccor

My bad. This seemed like the most relevant thread for issues with building qt5.

Unless you're a glutton for pain, it is much easier to use Alien Bob's precompiled binary. I tried building qt5 from a SlackBuild from SBo (with the required dependencies installed) on a clean VM on my low-powered htpc. It would usually fail around day 2 (over 48 hours compiling... I said it was low-powered

). I tried several times to fix this by giving more tmp space, increasing swap, increasing RAM (I basically ran the htpc barebones and only allotted 512MB for the OS and the remaining 7.5GB towards the VM with over 30GB of swap available, and it still failed. I then moved the VM to my high-powered desktop and it completed the compile without issue (8GB swap and 4GB RAM in the VM). qt5 can be quite fickle.

http://www.slackware.com/~alien/slac...t5/pkg64/14.2/

Just make sure you check out the .dep file and grab any dependencies needed for this package.

In other news, you're probably better to just create a new thread on issues rather than resurrecting an old thread. If you feel the old thread might be helpful for others to look at, you can provide links and/or quotes in your new thread. It helps prevent confusion like what happened here.

kevmccor · 03-24-2018, 07:26 AM

I need the Qt 5.9.4 which is in the /current folder. I am using 14.2 with the Qt 5.7.1 from SBo (only a few hours to compile, intel i5-3470T on my desktop). Since the build attempt for Qt 5.9.4 failed, I think the 5.9.4 package will probably not work either.

I will remember not to reply to old threads unless it is really on topic.

Thanks.

drgibbon · 03-27-2018, 09:40 PM

Quote:

Originally Posted by cdek

I built the version from Slackbuilds. It took an insane amount of time to build, but all went well. I installed it and everything seems to be working just fine. Thank you!

SBo scripts are usually fine, but if you're unsure you can always test to see if the package will overwrite anything on the system before installing:

Code:

installpkg --warn some-package.tgz

From the man page:

Quote:

--warn packagename

Generate a list of files that would be overwritten to the standard output, but do not actually install the package. The list is formatted in a suitable fashion to use as a list of files to backup.