gtk2 recursive directory error

Ryan Schmidt ryandesign at macports.org
Tue Dec 18 04:02:38 PST 2007


On Dec 17, 2007, at 14:52, Matrix Mole wrote:

> I was just upgrading gtk2 to get it compiled against a package that  
> was
> recently upgraded so I could remove the deactivated version of a port
> (don't remember which port as it was upgraded during a port -dRu
> outdated process). I noticed that gtk2 was taking a very long time to
> install, and then saw that it was downloading... again. When I  
> looked at
> the path it was installing into it was going to
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/.... to the
> 17th gtk2 nested directory. I checked each of those directories and
> noticed that for some reason gtk2 is downloading it's binary over and
> over again and recompiling itself, and appears to be stuck in an  
> endless
> loop.

Here's the ticket for this issue:

http://trac.macports.org/projects/macports/ticket/10827

> Here's the output of a 'find
> /opt/local/var/macports/distfiles/gtk2' command:
> /opt/local/var/macports/distfiles/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk+-2.10.13.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk+-2.10.14.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk 
> +-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk+-2.12.2.tar.bz2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2
> /opt/local/var/macports/distfiles/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/ 
> gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk2/gtk 
> +-2.12.2.tar.bz2

This is the ticket for this problem:

http://trac.macports.org/projects/macports/ticket/11971

> I'm using OS X 10.4.11 on a macbookpro model 1,1 and using the  
> macports
> version 1.60 that was just released. I don't know what version of  
> xcode
> I've got, could someone let me know where I can get that info?

Go to /Developer/Applications/, click on Xcode, and choose Get Info  
from the File menu. Then look at the Version field in the Info window.

> Not sure
> what else might be needed to help track down or resolve this problem.
> Oh, the command I used that resulted in this issue was 'sudo port -dfR
> upgrade glib2 gtk2 atk cairo' so I'm not sure if the command I used
> somehow managed to cause this issue.

That'll be it. Please do not use -f in combination with sudo port  
upgrade. Here's a ticket about that:

http://trac.macports.org/projects/macports/ticket/12989



More information about the macports-users mailing list