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: Kristopher Gamrat <pikidalto@...>
Date: Sat, 12 Mar 2011 23:59:55 -0500
On Sat, Mar 12, 2011 at 11:56 PM, David C. Rankin
<drankinatty@...> wrote:
> On 03/12/2011 10:51 PM, David C. Rankin 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()
>>
> <snip>
>
> Correction - this isn't just an x86_64 issue -- it effects all
> architectures. So it is a dependency issue. On the box that works, I have no
> problem getting:
>
> <snip>
> -- checking for one of the modules 'xext'
> -- checking for one of the modules 'xtst'
> -- checking for one of the modules 'xscrnsaver'
> <snip>
>
>  What makes the check for 'xscrnsaver' succeed?
>
> --
> David C. Rankin, J.D.,P.E.

Don't do that! I thought gmail was malfunctioning when it was still
unread after my reply! lol j/k Must've clicked send right when your
message arrived.

Maybe the other boxes are missing one of the three packages? My vote
would be to check for xext and xtst.

-- 
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager