https://bugs.kde.org/show_bug.cgi?id=386170

--- Comment #3 from shevegen <sheve...@gmail.com> ---
I wanted to add two more bits of information - not sure if they are
helpful, but additional information may be useful.

(1) My base system here on my main desktop machine, on which I also
reported the above situation, is slackware. But I compile the KDE
stack from source e. g. https://download.kde.org/stable/frameworks/5.39/
and https://download.kde.org/stable/applications/17.08.2/src/ and so
forth. I tend to use the /usr/ prefix normally but sometimes I also
use the GoboLinux versioned AppDir approach - so for example,
konsole would have the --prefix /Programs/Konsole/17.08.2, based on
the URL
 
https://download.kde.org/stable/applications/17.08.2/src/konsole-17.08.2.tar.xz

The latter approach requires of me to handle the cmake-modules of KDE
e. g. at /usr/lib/cmake/ (such as KF5 etc...) and I can not exclude
that I am doing everything right of course. But on the other hand, I
also was able to compile everything necessary up to (and including)
konsole from source, and konsole was even running fine. \o/

(2) I noticed that, the "s/" target, may have to do with "lib/". I
noticed this when I was compiling via versioned AppDir prefix, so
rather than a lib/ or lib64/ directory, I suddenly had a s/ directory.

I do not know if the latter observation is of any real help but I
just reported it in the event that it may be useful to others. I
could be wrong but some other KDE-related programs now seem to
use lib/ rather than lib64/, so I assume that perhaps this may be
related. But I am guessing here really.

I think that, either way, if it would be possible, it would be nice
to be able to understand the problem on the commandline since it
was unexpected to me via --prefix. I wrote a script for the latter
programs that replaces "s/" with "lib/" but this did not fix the 
issue, I still got error reports on a weird "lib/s/" prefix
instead.

I am not 100% sure but I can not remember this problem in the earlier
KDE releases from a few weeks ago, so I guess that there may have been
some changes. But I am really just guessing here mostly, sorry -
hopefully it may still be useful to someone out there. :)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to