Oh ye gods, not this fellow again.

Fellow gentoo-listers, please I beg you, with all my heart and all my
soul, I beg you:

Do not feed this troll. Please.

Alan



On 15/12/2017 16:44, Alan Grimes wrote:
> kdeinit:
> 
> over-tight constraint to cmake version:
> 
> ##################################
> -- Found XCB_XCB: /usr/lib/libxcb.so (found version "1.12")
> -- Found XCB: /usr/lib/libxcb.so (found version "1.12") found
> components:  XCB
> CMake Error at CMakeLists.txt:51 (find_package):
>   Could not find a configuration file for package "KF5KIO" that is
> compatible
>   with requested version "5.41.0".
> 
>   The following configuration files were considered but not accepted:
> 
>     /usr/lib64/cmake/KF5KIO/KF5KIOConfig.cmake, version: 5.40.0
>     /usr/lib/cmake/KF5KIO/KF5KIOConfig.cmake, version: 5.40.0
> 
> 
> 
> -- Configuring incomplete, errors occurred!
> See also
> "/var/tmp/portage/kde-frameworks/kinit-5.41.0/work/kinit-5.41.0_build/CMakeFiles/CMakeOutput.log".
> See also "/var/tmp/portage/kde-frameworks/kinit-5
> #################################
> 
> also the files symlink in the build path was a reference to itself!!! =P
> 
> 
> Also, the perennial fail, libcdio was giving a more helpful error
> message this time, seems it was looking for a specific libiconv even
> though that library seems to have been folded into glibc....
> 
> 
> 
> There is also a new perennial fail, that's very suspicious and worrying,
> ffmpeg... I think it might have to do with relocatable code or
> something, I thought I had disabled that feature and had gotten it to
> work, apparently some pinhead decided to turn it back on thinking 'ooh
> security'.  I'm like look: the only thing I care about is that I can log
> in. =|
> 
> In file included from src/libpostproc/postprocess.c:538:0:
> src/libpostproc/postprocess_template.c: In function ‘dering_MMX2’:
> src/libpostproc/postprocess_template.c:1097:5: error: ‘asm’ operand has
> impossible constraints
>      __asm__ volatile(
>      ^~~~~~~
> 
> 


-- 
Alan McKinnon
alan.mckin...@gmail.com


Reply via email to