Problem in cmake on kdeadmin-4.4.2

James Richard Tyrer tyrerj at
Sun Apr 25 13:38:40 PDT 2010

On 04/25/10 09:03, cliffhanger at wrote:
> -----Original Message-----
> From: James Richard Tyrer <tyrerj at>
> To: BLFS Support List <blfs-support at>
> Sent: Sun, Apr 25, 2010 4:37 pm
> Subject: Re: Problem in cmake on kdeadmin-4.4.2
> On 04/25/10 07:35, cliffhanger at wrote:
>> -----Original Message----- From: James Richard Tyrer<tyrerj at>
>>> The actual finding is done by a Python script: "" in:
>>> .../kdeadmin/system-config-printer-kde/cmake-modules
>>> I would try running that manually. Change to that directory and:
>>> python
>>> If I read it correctly, it prints: "Groovy" to standard output if
>>> it
>> is
>>> found. If not, the easiest way to check to see that PyCups is
>> installed
>>> correctly is to install it again.
>> Doing this returns me to prompt, with no response
>> OK, that is the problem. PyCups is not installed correctly
> Maybe, but see below. echo $? returned 1 by the way.
>> Maybe i need to install Pycups elsewhere as suggested by lux-integ?
>> AFAIK, you can't do that. It will automatically be installed with the
>> same prefix as Python.
>> I've tried editing with
>> path/to/python/site-packages/cupshelpers - this doesn't help with
>> system-config-printer either.
>> That isn't going to help if the Python script doesn't find (py)cups.
>> So, I would try installing PyCups again
> Thanks James, done that twice now and the same two files, and
> cups-1.0-py2.6.egg-info are installed under
> /usr/lib/python2.6/site-packages. These are the only two expected I
> assume? A file list on the web says yes.
This makes little sense.  It may be related to having Python installed 
in: "/usr/local" but Python should know where it is installed.  But, 
perhaps, some symbolic links to: "/usr" could help.

	/usr/bin/python -> /usr/local/bin/python
	/usr/lib/python -> /usr/local/lib/python
	/usr/include/python -> /usr/local/include/python

IIRC, I had to do that when I still had Python installed in: "/usr/local".

If it was CMake that couldn't find something, you can set the two CMake 
environment variables that very roughly correspond to the normal ones 
for AutoTools (but ONLY for specifying paths!):


and they use the same syntax as other PATH environment variables.

James Tyrer

Linux (mostly) From Scratch

More information about the blfs-support mailing list