On Thu, 21 Jun 2007 07:57:43 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote:

> Hi,
> On Wed, 2007-06-20 at 22:44 +0200, [EMAIL PROTECTED] wrote:
>> Here no error is shown. It ends with this output:
>> make[2]: Entering directory `/svn/gimp'
>> test -z "/opt/gimp/bin" || mkdir -p -- "/opt/gimp/bin"
>>   /usr/bin/install -c 'gimptool-2.0' '/opt/gimp/bin/gimptool-2.0'
>> test -z "/opt/gimp/lib/pkgconfig" || mkdir -p --  
>> "/opt/gimp/lib/pkgconfig"
>>   /usr/bin/install -c -m 644 'gimp-2.0.pc'
>> '/opt/gimp/lib/pkgconfig/gimp-2.0.pc'
>>   /usr/bin/install -c -m 644 'gimpthumb-2.0.pc'
>> '/opt/gimp/lib/pkgconfig/gimpthumb-2.0.pc'
>>   /usr/bin/install -c -m 644 'gimpui-2.0.pc'
>> '/opt/gimp/lib/pkgconfig/gimpui-2.0.pc'
>> make[2]: Leaving directory `/svn/gimp'
>> make[1]: Leaving directory `/svn/gimp'
> Looks like make install doesn't work recursively, it doesn't enter any
> subdirectories. Are you sure that the Makefile is really the Makefile
> that configure created? It looks like it is somehow messed up, perhaps
> kdevelop fiddled with it. Do you see a SUBDIRS variable in your
> Makefile?
> Sven

Thanks, yes I think that must be what happened. I was seeing to what point  
I could use kdev interface which does things like import gnome automake  
project, run automake, run configure.

I had rerun the tools from command line after I found this was not working  
but apparently this fails to correct what is broken.

I did a fresh checkout and all is fine now.

I've wasted enough time being lead astray by this so I cant get to the  
bottom of exactly what is happening, I want to get back to fixing lanczos  

The main point is I have a working Gimp and full debugging and variable  
eval in kdevelop which is great.

Thanks for your comments.
Gimp-developer mailing list

Reply via email to