dbus-glib is not building (0% CPU no error messages) when building Gimp2

[poubelle.beslin@…]

When building the Gimp 2 the building process stops with dbus-glib. No error messages are displayed and the CPU is 0% (iddle).

Configuration is iBook / G4 / 12" / 1.2GHz / 1.25 Gb / Tiger

Here is the output on the terminal:

"sudo port install gimp2
Password:
--->  Fetching aalib
--->  Attempting to fetch aalib-1.4rc5.tar.gz from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/
--->  Verifying checksum(s) for aalib
--->  Extracting aalib
--->  Applying patches to aalib
--->  Configuring aalib
--->  Building aalib with target all
--->  Staging aalib into destroot
--->  Installing aalib 1.4rc5_2
--->  Activating aalib 1.4rc5_2
--->  Cleaning aalib
--->  Fetching curl
--->  Attempting to fetch curl-7.17.1.tar.bz2 from http://curl.haxx.se/download/
--->  Verifying checksum(s) for curl
--->  Extracting curl
--->  Configuring curl
--->  Building curl with target all
--->  Staging curl into destroot
--->  Installing curl 7.17.1_0+darwin_8
--->  Activating curl 7.17.1_0+darwin_8
--->  Cleaning curl
--->  Fetching libart_lgpl
--->  Attempting to fetch libart_lgpl-2.3.19.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/libart_lgpl/2.3/
--->  Verifying checksum(s) for libart_lgpl
--->  Extracting libart_lgpl
--->  Applying patches to libart_lgpl
--->  Configuring libart_lgpl
--->  Building libart_lgpl with target all
--->  Staging libart_lgpl into destroot
--->  Installing libart_lgpl 2.3.19_2
--->  Activating libart_lgpl 2.3.19_2
--->  Cleaning libart_lgpl
--->  Fetching libexif
--->  Attempting to fetch libexif-0.6.16.tar.bz2 from http://downloads.sourceforge.net/libexif
--->  Verifying checksum(s) for libexif
--->  Extracting libexif
--->  Configuring libexif
--->  Building libexif with target all
^[[A--->  Staging libexif into destroot
--->  Installing libexif 0.6.16_1
--->  Activating libexif 0.6.16_1
--->  Cleaning libexif
--->  Fetching libgpg-error
--->  Attempting to fetch libgpg-error-1.6.tar.bz2 from http://ftp.gnupg.org/gcrypt/libgpg-error
--->  Verifying checksum(s) for libgpg-error
--->  Extracting libgpg-error
--->  Configuring libgpg-error
--->  Building libgpg-error with target all
--->  Staging libgpg-error into destroot
--->  Installing libgpg-error 1.6_0
--->  Activating libgpg-error 1.6_0
--->  Cleaning libgpg-error
--->  Fetching libgcrypt
--->  Attempting to fetch libgcrypt-1.2.4.tar.bz2 from http://ftp.gnupg.org/gcrypt/libgcrypt
--->  Verifying checksum(s) for libgcrypt
--->  Extracting libgcrypt
--->  Configuring libgcrypt
--->  Building libgcrypt with target all
--->  Staging libgcrypt into destroot
--->  Installing libgcrypt 1.2.4_1+darwin_8
--->  Activating libgcrypt 1.2.4_1+darwin_8
--->  Cleaning libgcrypt
--->  Fetching perl5.8
--->  Attempting to fetch perl-5.8.8.tar.bz2 from http://www.cpan.org/src/5.0/
--->  Verifying checksum(s) for perl5.8
--->  Extracting perl5.8
--->  Applying patches to perl5.8
--->  Configuring perl5.8
--->  Building perl5.8 with target all
--->  Staging perl5.8 into destroot
--->  Installing perl5.8 5.8.8_0+darwin_8
--->  Activating perl5.8 5.8.8_0+darwin_8
--->  Cleaning perl5.8
--->  Fetching p5-xml-parser
--->  Attempting to fetch XML-Parser-2.35.tar.gz from http://ftp.ucr.ac.cr/Unix/CPAN/modules/by-module/XML
--->  Verifying checksum(s) for p5-xml-parser
--->  Extracting p5-xml-parser
--->  Configuring p5-xml-parser
--->  Building p5-xml-parser with target all
--->  Staging p5-xml-parser into destroot
--->  Installing p5-xml-parser 2.35_0
--->  Activating p5-xml-parser 2.35_0
--->  Cleaning p5-xml-parser
--->  Fetching gnome-keyring
--->  Attempting to fetch gnome-keyring-2.20.1.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/gnome-keyring/2.20/
--->  Verifying checksum(s) for gnome-keyring
--->  Extracting gnome-keyring
--->  Configuring gnome-keyring
--->  Building gnome-keyring with target all
--->  Staging gnome-keyring into destroot
--->  Installing gnome-keyring 2.20.1_0
--->  Activating gnome-keyring 2.20.1_0
--->  Cleaning gnome-keyring
--->  Fetching xmlcatmgr
--->  Attempting to fetch xmlcatmgr-2.2.tar.gz from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/
--->  Verifying checksum(s) for xmlcatmgr
--->  Extracting xmlcatmgr
--->  Configuring xmlcatmgr
--->  Building xmlcatmgr with target all
--->  Staging xmlcatmgr into destroot
--->  Installing xmlcatmgr 2.2_1
--->  Activating xmlcatmgr 2.2_1
--->  Cleaning xmlcatmgr
--->  Fetching docbook-xml-4.1.2
--->  Attempting to fetch docbkx412.zip from http://www.oasis-open.org/docbook/xml/4.1.2/
--->  Verifying checksum(s) for docbook-xml-4.1.2
--->  Extracting docbook-xml-4.1.2
--->  Configuring docbook-xml-4.1.2
--->  Building docbook-xml-4.1.2 with target all
--->  Staging docbook-xml-4.1.2 into destroot
--->  Installing docbook-xml-4.1.2 4.1.2_1
--->  Activating docbook-xml-4.1.2 4.1.2_1
######################################################################
# As MacPorts does not currently have a post-deactivate hook, 
# you will need to ensure that you manually remove the catalog 
# entry for this port when you uninstall it.  To do so, run 
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.1.2/catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.1.2
--->  Fetching libxml2
--->  Attempting to fetch libxml2-2.6.30.tar.gz from http://xmlsoft.org/sources/
--->  Verifying checksum(s) for libxml2
--->  Extracting libxml2
--->  Configuring libxml2
--->  Building libxml2 with target all
--->  Staging libxml2 into destroot
--->  Installing libxml2 2.6.30_0
--->  Activating libxml2 2.6.30_0
--->  Cleaning libxml2
--->  Fetching docbook-xml-4.2
--->  Attempting to fetch docbook-xml-4.2.zip from http://www.oasis-open.org/docbook/xml/4.2/
--->  Verifying checksum(s) for docbook-xml-4.2
--->  Extracting docbook-xml-4.2
--->  Configuring docbook-xml-4.2
--->  Building docbook-xml-4.2 with target all
--->  Staging docbook-xml-4.2 into destroot
--->  Installing docbook-xml-4.2 4.2_0
--->  Activating docbook-xml-4.2 4.2_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook, 
# you will need to ensure that you manually remove the catalog 
# entry for this port when you uninstall it.  To do so, run 
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.2/catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.2
--->  Fetching docbook-xsl
--->  Attempting to fetch docbook-xsl-1.72.0.tar.bz2 from http://downloads.sourceforge.net/docbook
--->  Verifying checksum(s) for docbook-xsl
--->  Extracting docbook-xsl
--->  Configuring docbook-xsl
--->  Building docbook-xsl with target all
--->  Staging docbook-xsl into destroot
--->  Installing docbook-xsl 1.72.0_0
--->  Activating docbook-xsl 1.72.0_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook, 
# you will need to ensure that you manually remove the catalog 
# entry for this port when you uninstall it.  To do so, run 
# "xmlcatmgr remove nextCatalog /opt/local/share/xsl/docbook-xsl/catalog.xml".
######################################################################
--->  Cleaning docbook-xsl
--->  Fetching getopt
--->  Attempting to fetch getopt-1.1.4.tar.gz from http://software.frodo.looijaard.name/getopt/files/
--->  Verifying checksum(s) for getopt
--->  Extracting getopt
--->  Applying patches to getopt
--->  Configuring getopt
--->  Building getopt with target all
--->  Staging getopt into destroot
--->  Installing getopt 1.1.4_1
--->  Activating getopt 1.1.4_1
--->  Cleaning getopt
--->  Fetching libxslt
--->  Attempting to fetch libxslt-1.1.22.tar.gz from ftp://xmlsoft.org/libxslt/
--->  Verifying checksum(s) for libxslt
--->  Extracting libxslt
--->  Configuring libxslt
--->  Building libxslt with target all
--->  Staging libxslt into destroot
--->  Installing libxslt 1.1.22_0
--->  Activating libxslt 1.1.22_0
--->  Cleaning libxslt
--->  Fetching xmlto
--->  Attempting to fetch xmlto-0.0.18.tar.bz2 from http://cyberelk.net/tim/data/xmlto/stable/
--->  Verifying checksum(s) for xmlto
--->  Extracting xmlto
--->  Configuring xmlto
--->  Building xmlto with target all
--->  Staging xmlto into destroot
--->  Installing xmlto 0.0.18_3
--->  Activating xmlto 0.0.18_3
--->  Cleaning xmlto
--->  Fetching dbus
--->  Attempting to fetch dbus-1.0.2.tar.gz from http://dbus.freedesktop.org/releases/dbus
--->  Verifying checksum(s) for dbus
--->  Extracting dbus
--->  Configuring dbus
--->  Building dbus with target all
--->  Staging dbus into destroot
--->  Creating launchd control script
###########################################################
# A startup item has been generated that will aid in
# starting dbus with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.macports.dbus.plist
###########################################################
--->  Installing dbus 1.0.2_2
--->  Activating dbus 1.0.2_2
--->  Cleaning dbus
--->  Fetching dbus-glib
--->  Attempting to fetch dbus-glib-0.74.tar.gz from http://dbus.freedesktop.org/releases/dbus-glib
--->  Verifying checksum(s) for dbus-glib
--->  Extracting dbus-glib
--->  Configuring dbus-glib
--->  Building dbus-glib with target all"

[rwoodsmall@…]

debug log of dbus-glib build.

[poubelle.beslin@…]

I just removed dbus-glib to restart from a clean install and used the -v flag from ports the Terminal seems to end on this line

"/bin/sh ../../libtool --mode=execute ../../dbus/dbus-binding-tool --prefix=some_object --mode=glib-server --output=example-service-glue.h ./example-service.xml"

It seems we are not having a compiling issue but an executing issue of libtool. There is an empty file named example-service-glue.h.tmp that is created. If you remove the .tmp extension the make file goes to the next line and tries to create another .h file.

[rwoodsmall@…]

I can verify this is indeed an issue. Attempting to build on either a G4 or G5 running Leopard results in a hang. Attached is a log file of "port -vd install dbus-glib"

[julien.lusson@…]

Same here :(

I've erased all my MacPorts install and just run : sudo port install dbus-glib, and it stall at the same point. (PowerBook G4 under MacOSX.5.1)

I don't know if it's related, I've install the Xorg update (quick install) : ​http://wiki.x.org/wiki/XDarwin

[rhwood@…]

Is everyone reporting this problem running Leopard (OS X 10.5.1)?

[schroeder@…]

Same Problem here with 10.5.1

[marcel@…]

I have the same problem with 10.4.11 (intel) running macports 1.520

[chckens@…]

Replying to rhwood@macports.org:

Is everyone reporting this problem running Leopard (OS X 10.5.1)?

I see this on 10.4.11 PPC/G4, and the original report is from someone on "Tiger".

[darrenmcdonald@…]

Same problem here, 10.4.11/PPC G4.

[eric@…]

Same problem here, 10.5.1 Intel. The failing command is:

../../dbus/dbus-binding-tool --prefix=my_object --mode=glib-server --output=test-service-glib-glue.h ./test-service-glib.xml

When I execute that command by hand (having looked at 'ps' to see the working directory), it just hangs. dapptrace doesn't give me anything I understand since I am not familiar with Mac programming or the Dtrace facility, but if you tell me what options to give dapptrace or the underlying dtrace command I can get that output to you.

[mfajer@…]

Same problem here, 10.5.1 Intel. The failing command is the dbus-binding-tool as mentioned above.

[mfajer@…]

And again the same problem on a 10.4.11 Intel.

[patrick.kontschak@…]

Well, same Problem here, too, 10.4.11 Intel MacBook!

[vinc17@…]

Same problem on my G5 Power Mac, I can't build Liferea 1.4.9 because

dbus-binding-tool --mode=glib-server --prefix=liferea_dbus ./liferea_dbus.xml > dbus_wrap.c

hangs.

[julien.lusson@…]

I've made this change to the dbus-glib Portfile, and it works, but maybe it has side bad effects...

configure.args	--mandir=${prefix}/share/man #\
		#--enable-tests

[julien.lusson@…]

maybe can someone make this bug "critical" because it block a lot of ports ...

[rhwood@…]

Resolved in changeset:31695

[jonas@…]

This fix doesn't work for me. I've done a

sudo port -v clean --all dbus-glib

and the portfile has been updated accordingly.

I'm stuck at the same line as the second poster. I'm on a PB G4, 10.4.11.

[telecommunicationbreakdown@…]

Like the previous poster, I'm also on a PB G4 running 10.4.11, and still hang with no activity while building. As a previous poster suggested, perhaps this merits an elevated priority?

[vinc17@…]

Same problem. While dbus-glib @0.74_0 was built successfully in the past on my machine, its build now hangs.

[vinc17@…]

FYI, here's what sample gives on the dbus-binding-tool process:

Analysis of sampling pid 18352 every 10.000000 milliseconds
Call graph:
    1000 Thread_0117
      1000 start
        1000 _start
          1000 main
            1000 dbus_binding_tool_output_glib_server
              1000 g_spawn_async_with_pipes
                1000 fork_exec_with_pipes
                  1000 read_ints
                    1000 read
                      1000 read

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
        read        1000

[vinc17@…]

The problem comes from glib2 @2.14.4_1.

prunille:~> ps auxww | grep dbus-binding-tool
root     18352   0.0  0.1    33440   1860  pc  S+    1:06AM   0:00.11 /opt/local/var/macports/build/_Users_vinc17_software_dports_devel_dbus-glib/work/dbus-glib-0.74/dbus/.libs/dbus-binding-tool --prefix=some_object --mode=glib-server --output=example-service-glue.h ./example-service.xml
root     18395   0.0  0.1    31604   1268  pc  S+    1:06AM   0:00.02 glib-genmarshal --header --body --prefix=dbus_glib_marshal_some_object /var/tmp/dbus-binding-tool-c-marshallers.HOBO2T

glib-genmarshal, which hangs at the same time, is from the glib2 port. So, I deactivated glib2 @2.14.4_1 and reactivated my old glib2 @2.14.2_0, and dbus-glib built successfully.

I propose that the summary be changed to: glib2: glib-genmarshal makes dbus-binding-tool hang (preventing from building several ports).

[bvpeck@…]

I am having the same problems in OS X 10.4.11 intel MBP.

Is there a way to downgrade to glib2 @2.14.2_0 so I can get around this until the bug is fixed? Thanks

[mfajer@…]

Resolved in changeset:31695

This change has indeed resolved my building process on an OS X 10.5.1 Intel MBP. Are those who are still having problems all on 10.4? I will check my second computer later today.

[junk@…]

I am on 10.4.11, PowerPC, yes.

[vinc17@…]

mfajer: which glib2 version do you use?

[grahamperrin@…]

+1

Syptoms are evident on
Mac OS X Server 10.4.11,
Power PC (Macintosh Server G4)

​http://paste.lisp.org/display/51995

[telecommunicationbreakdown@…]

I'm still unable to build as well (PPC 10.4.11).

[rhwood@…]

Ryan, can take a look at this? It may be a glib2 bug, not a dbus-glib bug.

[grahamperrin@…]

​debug output from
sudo port -d install wv

I'm often in IRC if any further input is needed.

Thanks!

---

Incidentally I do already have wv active on two other Macs, one of which is a PowerPC; as a workaround, can I copy selected files from one system to another?

[grahamperrin@…]

​abridged result of `sudo make -d` for dbus-glib-0.74.

Unabridged result is too an annotation to that paste so instead, I'll attach it as a file.

[grahamperrin@…]

unabridged result of sudo make -d for dbus-glib-0.74

[jzenker@…]

Replying to vinc17@macports.org:

The problem comes from glib2 @2.14.4_1. glib-genmarshal, which hangs at the same time, is from the glib2 port. So, I deactivated glib2 @2.14.4_1 and reactivated my old glib2 @2.14.2_0, and dbus-glib built successfully.

Good observation! I confirm that rolling back to glib2 @2.14.2_0 on my PowerBook G4 running 10.4.11 is an effective workaround. The commands needed to accomplish this are

sudo port deactivate glib2 @2.14.4_1
sudo port activate glib2 @2.14.2_0

It may also be necessary to clean other ports that depend on glib2.

[junk@…]

I've never had installed an earlier version of glib2. So activating an older version doesn't work for me, and 'install' results in the latest version being installed. Is there a way I can roll back?

[boeyms@…]

Replying to junk@lessjunkmorefunk.de:

You can roll back by creating a local ports tree and placing an older version of glib2 Portfile in it to mask the official one. The following instructions tell you how to do so from scratch (I hope you can work out what to omit if you've done some of these before).

1. Create a directory on your system to root your local ports tree in, e.g. /Users/me/mp-local-ports.

2. Create a subdirectory in that root into which to place the Portfile; it must match that reported by port search, which is in the form of a category and then a port name. In this case, we can see that glib2 is listed by port search ^glib2$ as being in devel/glib2:

   MyComputer:~ me$ port search ^glib2$
   glib2                          devel/glib2    2.14.4       Library with data structure functions and other constructs
   MyComputer:~ me$
   

   Thus the subdirectory to create is devel/glib2 (making the absolute path to the Portfile /Users/me/mp-local-ports/devel/glib2 in this case).

3. Copy the desired Portfile into the above directory -- if you want the one for glib2 @2.14.2_0, ​this patch should do the trick, otherwise you can browse ​the revisions to it for the one you want.

4. In this case, the Portfile demands patchfiles, which are stored in a files/ subdirectory of the port. You will thus need to create such a directory (e.g. /Users/me/mp-local-ports/devel/glib2/files) and copy the appropriate patchfiles into it (which in this case are ​here.

5. Return to the root of the local ports tree (e.g. /Users/me/mp-local-ports) and run portindex; this creates a PortIndex file in that directory that port can then use to know that your local port exists.

6. Finally, edit your ${prefix}/etc/macports/sources.conf file by putting the root directory of your local ports tree before the main rsync://rsync.macports.org/release/ports one, so that your local ports tree does indeed mask the official one. Note that the path must be in URL format, so in this case we would enter file:///Users/me/mp-local-ports.

Now installing glib2 (when it's not currently installed) will install the version whose Portfile you put into your local ports tree. Once you're done with it, simply delete the directory for that port, re-run portindex in the root of the local port tree, and uninstall the port; subsequent installs will once again pick up the official Portfile.

I hope this is straightforward enough to follow. If not, please say so.

[grahamperrin@…]

For reference, regarding glib2:
​http://trac.macports.org/projects/macports/browser/trunk/dports/devel/glib2

[brett@…]

Could someone please remove me as a CC? I no longer need to be updated on this issue. Email address brett@… . Thanks!

[grahamperrin@…]

Abstracting from comment 33 onwards, following advice from jmpp I have created a separate ticket ​issue with glib2 @2.14.4_1 and/or glib-genmarshal - so, can not build/install dbus-glib, Gimp2, wv etc..

[telecommunicationbreakdown@…]

Replying to boeyms@macports.org:

Replying to junk@lessjunkmorefunk.de: ... I hope this is straightforward enough to follow. If not, please say so.

Thanks very much for this! GIMP 2.4.2 is up and running on my PPC/10.4.11.

This is pretty much my first experience with MacPorts, so I needed a bit more info to get this working. For other newbies, it's also helpful to note that

1. You have to remove the .txt extension from the Portfile to get it to work (By right clicking on the file>Get Info> name & extension> then remove the .txt extension.)
2. From the pages for the individual patches, you have to go to the bottom and select "download in other formats: Original format". (Just right clicking on the links and selecting "Save linked file" only gets you html).

[rb@…]

Replying to boeyms@macports.org:

Replying to junk@lessjunkmorefunk.de:

You can roll back by creating a local ports tree and placing an older version of glib2 Portfile in it to mask the official one. The following instructions tell you how to do so from scratch (I hope you can work out what to omit if you've done some of these before).

1. Create a directory on your system to root your local ports tree in, e.g. /Users/me/mp-local-ports.

2. Create a subdirectory in that root into which to place the Portfile; it must match that reported by port search, which is in the form of a category and then a port name. In this case, we can see that glib2 is listed by port search ^glib2$ as being in devel/glib2:

   MyComputer:~ me$ port search ^glib2$
   glib2                          devel/glib2    2.14.4       Library with data structure functions and other constructs
   MyComputer:~ me$
   

   Thus the subdirectory to create is devel/glib2 (making the absolute path to the Portfile /Users/me/mp-local-ports/devel/glib2 in this case).

3. Copy the desired Portfile into the above directory -- if you want the one for glib2 @2.14.2_0, ​this patch should do the trick, otherwise you can browse ​the revisions to it for the one you want.

4. In this case, the Portfile demands patchfiles, which are stored in a files/ subdirectory of the port. You will thus need to create such a directory (e.g. /Users/me/mp-local-ports/devel/glib2/files) and copy the appropriate patchfiles into it (which in this case are ​here.

5. Return to the root of the local ports tree (e.g. /Users/me/mp-local-ports) and run portindex; this creates a PortIndex file in that directory that port can then use to know that your local port exists.

6. Finally, edit your ${prefix}/etc/macports/sources.conf file by putting the root directory of your local ports tree before the main rsync://rsync.macports.org/release/ports one, so that your local ports tree does indeed mask the official one. Note that the path must be in URL format, so in this case we would enter file:///Users/me/mp-local-ports.
   

I have followed the instructions closely and cannot get 'port' to read the portfile in /Users/pm/mp-local-ports. My macports.conf file reads:

# Rsync server to use

rsync_server ​file:///Users/pm/mp-local-ports

rsync_server rsync.macports.org

after running

port deactivate glib2

port -f uninstall glib2

port install glib 2

port fetches glib2 2.14.4_1

Any pointer to what I am doing wrong would be appreciated. Thank you.

[telecommunicationbreakdown@…]

Replying to rb@panix.com:

I have followed the instructions closely and cannot get 'port' to read the portfile in /Users/pm/mp-local-ports. My macports.conf file reads:

# Rsync server to use

rsync_server ​file:///Users/pm/mp-local-ports

rsync_server rsync.macports.org

after running

port deactivate glib2

port -f uninstall glib2

port install glib 2

port fetches glib2 2.14.4_1

Any pointer to what I am doing wrong would be appreciated. Thank you.

You don't need the 'rsync_server' bit in front of the '​file://...' line in the sources.conf file. And it's the sources.conf file that needs to be modified, not macports.conf. Maybe that's it?

[rb@…]

Replying to telecommunicationbreakdown@hotmail.com:

Replying to rb@panix.com:

I have followed the instructions closely and cannot get 'port' to read the portfile in /Users/pm/mp-local-ports. My macports.conf file reads:

# Rsync server to use

rsync_server ​file:///Users/pm/mp-local-ports

rsync_server rsync.macports.org

after running

port deactivate glib2

port -f uninstall glib2

port install glib 2

port fetches glib2 2.14.4_1

Any pointer to what I am doing wrong would be appreciated. Thank you.

You don't need the 'rsync_server' bit in front of the '​file://...' line in the sources.conf file. And it's the sources.conf file that needs to be modified, not macports.conf. Maybe that's it?

Thank you, that was exactly it. I should have said I "...tried to follow instructions closely"

Now I am getting the following error:

paolo% sudo port install glib2

Password: ---> Applying patches to glib2 Error: Target org.macports.patch returned: shell command " cd "/opt/local/var/macports/build/_Users_pm_mp-local-ports_devel_glib2/work/glib-2.14.2" && patch -p0 < '/Users/pm/mp-local-ports/devel/glib2/files/patch-glib-2.0.pc.in.diff'" returned error 2 Command output: patch: Only garbage was found in the patch input.

Error: Status 1 encountered during processing.

Any idea about this one? Thanks

[telecommunicationbreakdown@…]

Replying to rb@panix.com:

Command output: patch: Only garbage was found in the patch input.

Error: Status 1 encountered during processing.

Any idea about this one? Thanks

Yeah, for this one you need to go to the pages for the patches, scroll to the bottom of the page, and select "Original format" under the "download in other formats" options in the center of the page. (Otherwise you just get the html files, aka garbage.)

[Fawzi_Masri@…]

Hello,

---> Building dbus-glib with target all--> Hangs

dbus-glib is still a problem while installing gimp2.

there is a lot of discussion on this, but really it does not help someone like me coming in the middle of the discussion.

can we expect a fix for 10.4.11 ppc sometime soon?

regards,

(Macport version: 1.600)

[ryandesign (Ryan Carsten Schmidt)]

I cannot reproduce this problem on my MacBookPro3,1 with Mac OS X 10.4.11 and Xcode 2.4.1, and I don't know what to do about it, so I ​filed a bug with the developers of glib.

[rb@…]

Replying to telecommunicationbreakdown@hotmail.com:

Replying to rb@panix.com:

Command output: patch: Only garbage was found in the patch input.

Error: Status 1 encountered during processing.

Any idea about this one? Thanks

Yeah, for this one you need to go to the pages for the patches, scroll to the bottom of the page, and select "Original format" under the "download in other formats" options in the center of the page. (Otherwise you just get the html files, aka garbage.)

Thank you again. glib2 @2.14.2_0 and dbus-glib now built and installed.

One more question: in the original step-by-step, the final instruction calls for uninstalling the port

"Now installing glib2 (when it's not currently installed) will install the version whose Portfile you put into your local ports tree. Once you're done with it, simply delete the directory for that port, re-run portindex in the root of the local port tree, and uninstall the port; subsequent installs will once again pick up the official Portfile."

Is this necessary? Should it be done before I complete the installation of the app (gnucash2) I need glib2 and dbus-glib for? Thank you.

[telecommunicationbreakdown@…]

Replying to rb@panix.com:

One more question: in the original step-by-step, the final instruction calls for uninstalling the port

"Now installing glib2 (when it's not currently installed) will install the version whose Portfile you put into your local ports tree. Once you're done with it, simply delete the directory for that port, re-run portindex in the root of the local port tree, and uninstall the port; subsequent installs will once again pick up the official Portfile."

Is this necessary? Should it be done before I complete the installation of the app (gnucash2) I need glib2 and dbus-glib for? Thank you.

This I don't know about, but I didn't bother uninstalling the port, and I left everything as it was when I built the gimp. Didn't cause any problems here!

[ddp@…]

Just a note that dbus-glib ends up in the dependency graph of firefox-x11 these days (from gnome-vfs), so this is blocking a lot of other ports...

Thanks for posting the instructions on how to insert a shadow port directory, I've been needing that for a while. I did have to roll back all four ​patch files as they were renamed between 2.14.0 and 2.14.4. The previous versions built fine with the ​2.14.0 Portfile and dbus-glib is now happily installed.

If I may answer the last two folks, no you don't have to delete the local port directory you created, but you will want to clean it up at some point or it will continue overriding MacPorts. Then again, being able to freeze a particular version of a port could be viewed as a feature, depending on what you're trying to build and your personal tolerance to feature creep. :-)

[ryandesign (Ryan Carsten Schmidt)]

In the notes of ​the bug I filed with the glib developers, someone said that glib 2.14.5 no longer has this problem, due to the fix for ​this bug, so I updated the port in r32728. Please wait 12 hours, then "sudo port selfupdate", then "sudo port upgrade glib2". Please let me know whether or not glib 2.14.5 fixes the dbus-glib / dbus-binding-tool / glib-genmarshal hang.

[grahamperrin@…]

​dbus-glib installed successfully on Intel MacBook Pro running Mac OS X 10.4.11.

[grahamperrin@…]

​dbus-glib installed successfully on PowerPC Power Mac G4 running Mac OS X Server 10.4.11.

Not tested by me:

• sudo port install dbus-glib on Mac OS X 10.5 on PowerPC
• sudo port install dbus-glib on Mac OS X 10.5 on Intel.

Many thanks to ryandesign for progressing this!

[rhwood@…]

I've installed this on a PPC running Mac OS X 10.5, so I think we have covered our bases with Graham's tests on Mac OS X 10.4.

[(none)]

Milestone Port Bugs deleted