trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2011

Re: [trinity-devel] kpowersave on x86_64 - pkg_search_module( XSCRNSAVER xscrnsaver ) fails??

From: calvin morrison <mutantturkey@...>
Date: Sun, 13 Mar 2011 07:33:20 -0400
On 12 March 2011 23:57, Kristopher Gamrat <pikidalto@...> wrote:
> On Sat, Mar 12, 2011 at 11:51 PM, David C. Rankin
> <drankinatty@...> wrote:
>> Guys,
>>
>>   I can't explain this one. On i686, kpowersave built fine, but on x86_64,
>> the build fails due to:
>>
>> CMake Error at cmake/modules/TDEMacros.cmake:20 (message):
>>  #################################################
>>
>>   xscrnsaver are required, but not found on your system
>>
>>  #################################################
>> Call Stack (most recent call first):
>>  ConfigureChecks.cmake:42 (tde_message_fatal)
>>  CMakeLists.txt:40 (include)
>>
>>
>> -- Configuring incomplete, errors occurred!
>>
>> In ConfigureChecks.cmake, we have:
>>
>> # check for xscrnsaver
>> pkg_search_module( XSCRNSAVER xscrnsaver )
>> if( NOT XSCRNSAVER_FOUND )
>>  tde_message_fatal( "xscrnsaver are required, but not found on your system"
>> )
>> endif()
>>
>>  On Arch the package is actually xscreensaver. On both i686 and x86_64
>> boxes, I have 'xscreensaver 5.12-2' installed, but for some reason, this
>> works on i686. Dunno why...
>>
>>  Where can I look at the actual code for "pkg_search_module()" so I can tell
>> exactly what it is looking for? It almost seems like I've run into this
>> before, but can't recall for the life of me what I did to address it?
>>
>>  There must be some other package on the box that works that provides the
>> dependency that kpowersave is looking for, but how do I figure that out?
>> What say the experts?
>>
>>
>> --
>> David C. Rankin, J.D.,P.E.
>
> Normally it is forgetting to install the devel package. Or it may be
> looking for the 32bit version of xscreensaver, which means it would
> need adjusted to check for 64bit. You probably know this, but 64bit
> libs tend to go into lib64 instead of lib, so that might be where it
> fails because some stuff have it hardcoded to assume 32bit libs. Of
> course, I couldn't understand the code very well, so I couldn't tell
> you for sure.
>
> --
> Kris
> "Piki"
> Ark Linux Webmaster
> Trinity Desktop Environment Packager

All of those assumptions here are wrong for arch :) we don't have
devel packages and we don't have a lib64