gconf @2.28.1 Failed to install

[ade_hall@…]

Inexperienced macports user, did a selfupgrade and update outdated and got errors, then did a clean on gconf and then install

[ryandesign (Ryan Carsten Schmidt)]

Please "sudo port clean gconf" and try again. Cleaning and trying again is the first thing you should try anytime any port fails to build. If it fails again after that, attach the new main.log file.

[ade_hall@…]

Same results, have also included the terminal logs in the attachment

[ade_hall@…]

Terminal + Main logs

[ryandesign (Ryan Carsten Schmidt)]

The terminal transcript you provided shows that MacPorts:

• installed the pre-built gconf-2.28.1_3.darwin_10.x86_64.tbz2 package from our server
• rev-upgrade ran, which detected that this gconf was in fact broken in some way
• tried to build gconf from source on your system, which failed
• rev-uprade determined gnome-vfs was broken
• tried to rebuild gnome-vfs, but since it depends on gconf, tried again to build gconf, without cleaning it first, and it failed again
• repeated the above step once more
• exited

We need to see the clean logs of the gconf build, but the above steps mean that MacPorts left you with an unclean log again. I'm Cc'ing Clemens, who wrote the rev-upgrade feature for us, because this behavior doesn't seem optimal.

ahe_hall, please run "sudo port clean gconf", then run "sudo port -s install --no-rev-upgrade gconf". "-s" means build from source; don't use the binary from our server. "--no-rev-upgrade" means that even if MacPorts thinks things are broken after installation, it should not try to rebuild things to fix them. Presumably this build will fail and you can then attach that main.log to this ticket, which will hopefully contain enough information to help us diagnose the problem.

We did already have one other report of gconf failing to build. There I suggested we might need to update gconf to a newer version. So that's something we can try.

[ryandesign (Ryan Carsten Schmidt)]

Cc Me!

[neverpanic (Clemens Lang)]

This looks a lot like #33792. Did you recently upgrade your Xcode version? Can you try rebuilding libidl, cleaning gconf and trying again?

[ade_hall@…]

Same results. I did upgrade to 4.2 sometime ago. Is it worth updating to a newer gconf as suggested above?

[ryandesign (Ryan Carsten Schmidt)]

The transcript does not show you rebuilding libidl. You should rebuild it like this:

sudo port clean libidl
sudo port -ns upgrade --force libidl

Then clean gconf and try again.

[ade_hall@…]

Thanks for your help and patience, this has fixed it

[neverpanic (Clemens Lang)]

Duplicate of #33792.