Slackware 14.2 multilib - Telepathy-Qt fails to build

glupa4e · 07-04-2017, 02:40 PM

Hello i was trying to install the current version of the package Telepathy-Qt available here. All dependencies seem to be satisfied. When i begin building the package i encounter:

Code:

[ 11%] Building CXX object TelepathyQt/CMakeFiles/telepathy-qt4-service.dir/base-channel.cpp.o
In file included from /tmp/SBo/telepathy-qt-0.9.6.1/TelepathyQt/base-channel.cpp:29:0:
/tmp/SBo/telepathy-qt-0.9.6.1/TelepathyQt/future-internal.h:26:47: fatal error: TelepathyQt/_gen/future-constants.h: No such file or directory
compilation terminated.
TelepathyQt/CMakeFiles/telepathy-qt4-service.dir/build.make:182: recipe for target 'TelepathyQt/CMakeFiles/telepathy-qt4-service.dir/base-channel.cpp.o' failed
make[2]: *** [TelepathyQt/CMakeFiles/telepathy-qt4-service.dir/base-channel.cpp.o] Error 1
CMakeFiles/Makefile2:5232: recipe for target 'TelepathyQt/CMakeFiles/telepathy-qt4-service.dir/all' failed
make[1]: *** [TelepathyQt/CMakeFiles/telepathy-qt4-service.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

Any idea what i could be missing or doing wrong?

Darth Vader · 07-04-2017, 04:11 PM

The Multilib Way, with all respect for Eric's hard work, is basically just dumping Slackware (i586) and Slackware x86_64 in the same bin and mixing energetically the result.

Simplify your life and create (secondary) clean installations for both Slackware (i586) and Slackware x86_64, then compile on them as you wish.

Quote:

Originally Posted by glupa4e

Any idea what i could be missing or doing wrong?

The fantasy that you can dump two different operating systems in the same partition, and even to do compilations.

55020 · 07-04-2017, 04:34 PM

glupa4e, could you try editing the SlackBuild so it says 'make -j1' at line 89 instead of just 'make'?

And if that still fails, could you please put the complete log on a pastebin site somewhere?

(_gen/future-constants.h should have been created as the second thing built by the MakeFile, and base-channel.cpp.o should not be built until much later, "54%" according to my test build.)

RadicalDreamer · 07-05-2017, 02:16 AM

I tried on current multilib to see what would happen. It was built completely without any of those dependencies installed.

Code:

Done building package for telepathy-qt.
Built package: telepathy-qt-0.9.6.1-x86_64-1_SBo.tgz

glupa4e · 07-05-2017, 12:49 PM

Quote:

Originally Posted by 55020

glupa4e, could you try editing the SlackBuild so it says 'make -j1' at line 89 instead of just 'make'?

And if that still fails, could you please put the complete log on a pastebin site somewhere?

(_gen/future-constants.h should have been created as the second thing built by the MakeFile, and base-channel.cpp.o should not be built until much later, "54%" according to my test build.)

Hi 55020,
i tried what you suggested. The build failed again. Full log of the error can be found as you wished here.
thanks!

55020 · 07-07-2017, 03:39 AM

Ok I've just built telepathy-qt-0.9.6.1 on 14.2 with multilib, and it built ok just like RadicalDreamer on -current.

My only suggestion is to make sure you have a full, clean, up-to-date installation. I wonder what version of make you have installed? And your log shows that you have out-of-date versions of python (2.7.11) and pkg-config (0.29.1). Both these packages and many more have been patched in the 14.2 stable branch.

phenixia2003 · 07-07-2017, 04:42 AM

Hello,

The issue reported here looks like the issue encountered by the OP. According to comment #5, the commits below should solve the issue :

BaseChannel: Reduced includes (doesn't depend on client stuff anymore)

CMakeLists: Added missing service dependence.

--
SeB

Darth Vader · 07-07-2017, 08:43 AM

How about to use just a operating system for compilation, instead of TWO?

For the sake of gods, I wish somewhere to be written: "Going multi-lib, you lose your rights to compile something from sources!"

Darth Vader · 07-07-2017, 08:46 AM

Quote:

Originally Posted by 55020

Ok I've just built telepathy-qt-0.9.6.1 on 14.2 with multilib, and it built ok just like RadicalDreamer on -current.

For which target? x86? x86_64? Gods know?

glupa4e · 07-07-2017, 01:01 PM

Quote:

Originally Posted by phenixia2003

Hello,

The issue reported here looks like the issue encountered by the OP. According to comment #5, the commits below should solve the issue :

BaseChannel: Reduced includes (doesn't depend on client stuff anymore)

CMakeLists: Added missing service dependence.

--
SeB

Hi phenixia2003,
i am sorry i have no idea what those commits mean and how i could patch my installation. Could you help me understand what i need to do?

glupa4e · 07-07-2017, 01:06 PM

Quote:

Originally Posted by 55020

Ok I've just built telepathy-qt-0.9.6.1 on 14.2 with multilib, and it built ok just like RadicalDreamer on -current.

My only suggestion is to make sure you have a full, clean, up-to-date installation. I wonder what version of make you have installed? And your log shows that you have out-of-date versions of python (2.7.11) and pkg-config (0.29.1). Both these packages and many more have been patched in the 14.2 stable branch.

Hi 55020,

when i initially installed Slackware 14.2 64 i performed a full installation. I do not know what you mean by clean but after the initial installation i have done some upgrades but as i am having problems (some packages fail to build) i do not upgrade everything.

So you say i have outdated packages. Could you please point me how to check for the version of the packages i have and where to download a recent version for those ones. I found nothing what you listed on slackware.uk.

montagdude · 07-07-2017, 01:10 PM

Quote:

Originally Posted by glupa4e

Hi 55020,

when i initially installed Slackware 14.2 64 i performed a full installation. I do not know what you mean by clean but after the initial installation i have done some upgrades but as i am having problems (some packages fail to build) i do not upgrade everything.

So you say i have outdated packages. Could you please point me how to check for the version of the packages i have and where to download a recent version for those ones. I found nothing what you listed on slackware.uk.

Do you use slackpkg? If so,

Code:

slackpkg update && slackpkg upgrade-all

should ensure that everything is up-to-date. If you have removed packages after installing, you can try:

Code:

slackpkg install slackware64

which will bring up a list of anything from a full installation that is not on your system.

EDIT: I forgot to mention, you should also check /etc/slackpkg/blacklist, as anything in that file will be ignored when you run slackpkg.

phenixia2003 · 07-08-2017, 05:59 AM

Hello,

Quote:

Originally Posted by glupa4e

Hi phenixia2003,
i am sorry i have no idea what those commits mean and how i could patch my installation. Could you help me understand what i need to do?

1. Download the patches below :

BaseChannel-Reduced-includes.patch.txt
CMakeLists-Added-missing-service-dependence.patch.txt
telepathy-qt.SlackBuild.patch.txt

2. copy the patches into your telepathy-qt directory without the .txt extension :

Code:

$ cp BaseChannel-Reduced-includes.patch.txt telepathy-qt/BaseChannel-Reduced-includes.patch

$ cp CMakeLists-Added-missing-service-dependence.patch.txt telepathy-qt/CMakeLists-Added-missing-service-dependence.patch

$ cp telepathy-qt.SlackBuild.patch.txt telepathy-qt/telepathy-qt.SlackBuild.patch

Once you did that, your telepathy-qt must contain the files below :

Code:

$ cd telepathy-qt
$ ls -1
BaseChannel-Reduced-includes.patch
CMakeLists-Added-missing-service-dependence.patch
README
glibc.patch
gstreamer.patch
slack-desc
telepathy-qt-0.9.6.1.tar.gz
telepathy-qt.SlackBuild
telepathy-qt.SlackBuild.patch
telepathy-qt.info

3. in your telepathy-qt directory, update the script telepathy-qt.SlackBuild as below :

Code:

$ cd telepathy-qt
$ patch -p0<telepathy-qt.SlackBuild.patch

At this point, telepathy-qt.SlackBuild must include the code below :

Code:

# Fix bug 93707
# https://bugs.freedesktop.org/show_bug.cgi?id=93707#c5
#
patch -p0 < $CWD/BaseChannel-Reduced-includes.patch
patch -p0 < $CWD/CMakeLists-Added-missing-service-dependence.patch

4. Try to rebuild telepathy-qt to check if this solve your issue.

--
SeB

kjhambrick · 07-08-2017, 06:49 AM

Thank you for the excellent HOWTO, phenixia2003 !

I wanted to try your instructions but I didn't because of the REQUIRES= Hierarchy for the telepathy-qt.SlackBuild.

These are the prerequisites ( in install order ) for multimedia/telepathy-qt:

Code:

1. libraries/libnice
2. multimedia/farstream
3. multimedia/telepathy-glib
4. multimedia/telepathy-farstream

I don't need telepathy-qt nor any of the prerequisites as far as I know, but it sure looks like your HOWTO will work just fine.

The prerequisites look harmless-enough to install on Slackware64 14.2 + Multilib ... I am simply too lazy to install and maintain the additional Packages

Q1: Based on the $-prompt, you execute your SBo SlackBuilds as a non-root user.

Does that always work ?

I did not know I could execute SBo SlackBuilds as non-root. If so, I am changing my evil, log in as root ways in order to execute SBo SlackBuilds !

Q2: ( OT, LQ Question ) How did you embed the patch.txt file links in the body of your Post without an attachment list below your signature ?

That is a very nice format -- very clean and easy to follow.

Thanks again !

-- kjh

55020 · 07-08-2017, 08:18 AM

Quote:

Originally Posted by kjhambrick

Q1: Based on the $-prompt, you execute your SBo SlackBuilds as a non-root user.

No, SeB's post shows the SlackBuild itself being patched by a non-root user before execution, but it doesn't show how SeB executes the SlackBuild.

Despite that, you can, if you want to, use fakeroot to run SBo SlackBuilds as a non-root user.

Quote:

Originally Posted by kjhambrick

Does that always work ?

I did not know I could execute SBo SlackBuilds as non-root. If so, I am changing my evil, log in as root ways in order to execute SBo SlackBuilds !

No, it doesn't always work. I wouldn't describe using root as evil, and I wouldn't particularly recommend using fakeroot. (Specifically, I use it when I review submissions and updates so you don't have to.)