I forced an install and upgraded 'dbus', and then every package that
was outdated on the file list. Some of these did not show up in an
outdated listing. I only discovered them when they failed during the
forced 'dbus' upgrade. With dependencies it took 3 days to get every
thing updated.
The problems that showed up included packages 'libgnomekbd' and
'control-center'. At one point a file reference was extracted called "
lbxslt" for which I was informed no such file existed... So somewhere
there is an error reference to a file 'libxslt' that was incorrectly
entered in the latest Macports update. Other packages that showed up
with errors during the dependency installs included 'guile16', 'gperf
3.02_0' and 'XFree86 4.6.0_0'. I did nothing about them.
So back to GnuCash.
I just tried to install it again and after a bunch of dependencies that
went in without a hitch I got this error:
---> Fetching gnucash
---> Attempting to fetch gnucash-2.0.5.tar.gz from
http://www.gnucash.org/pub/gnucash/sources/stable/
---> Verifying checksum(s) for gnucash
---> Extracting gnucash
---> Configuring gnucash
Error: Target com.apple.configure returned: configure failure: shell
command " cd
"/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_gnome_gnucash/work/gnucash-2.0.5"
&& ./configure --prefix=/opt/local --disable-glibtest
--disable-debug --disable-profile --disable-dependency-tracking
--enable-hbci --enable-ofx " returned error 1
Command output: checking for dlerror... yes
checking for darwin... yes, moving on...
checking for qt_null in -lqthreads... no
checking for qt_null in -lqt... no
checking for main in -ltermcap... yes
checking for main in -lreadline... yes
checking for guile-config... yes
checking whether guile-config works... yes
checking for sin in -lm... yes
checking for guile libraries... -D_THREAD_SAFE -lguile -lltdl
-L/opt/local/lib -L/opt/local/lib -lgmp -lm -lltdl
checking for guile headers... -I/opt/local/include -D_THREAD_SAFE
checking whether guile works... yes
checking for guile... /opt/local/bin/guile
checking for guile - 1.6.0 <= version < 99.99.99... yes: 1.8.1
checking for guile - 1.8.0 <= version < 99.99.99... yes: 1.8.1
checking for g-wrap-config... /opt/local/bin/g-wrap-config
checking for g-wrap - version >= 1.3.3... yes
checking for g-wrap compile args... -I /opt/local/include/g-wrap
checking for g-wrap link args... -L/opt/local/lib -lgwrap-wct
-lgwrap-glib
checking for g-wrap module directory... /opt/local/share/guile
checking g-wrap-wct.h usability... yes
checking g-wrap-wct.h presence... yes
checking for g-wrap-wct.h... yes
checking for (g-wrap) guile module... configure: error:
Cannot find the (g-wrap) guile module.
Are you sure you have g-wrap compile-time environment installed?
See http://bugzilla.gnome.org/show_bug.cgi?id=347680
Error: Status 1 encountered during processing.
So now what? What is a (g-wrap) guile module? And how is it configured?
Or is it the real problem?
Bj
Boey Maun Suang wrote:
Hi Bjorn,
On 23/04/2007, at 13:42, Bjorn Berg wrote:
So after 6 hours of an attempted uninstall,
this is all I've got:
bj$ sudo port -f uninstall dbus Password:
---> The following versions of dbus are currently installed:
---> dbus @0.61_2 (active)
---> dbus @1.0.2_2
Error: port uninstall failed: Registry error: Please specify the full
version as
recorded in the port registry.
IBook:~ bj$ sudo port -f uninstall dbus @0.61_2
Password:
---> Unable to uninstall dbus 0.61_2, the following ports depend on
it:
---> gnome-vfs
Warning: Uninstall forced. Proceeding despite dependencies.
---> Deactivating dbus 0.61_2
I could let the thing stagnate for a week but I think it's hopeless.
Obviously deactivating dbus, even though there aren't any programs
running (I rewrote my .xinitrc file so gnome is not active because I
thought it might hang otherwise. It hung anyway.), is going to be a
long and arduous process. This dbus 0.61_2 version appears to be too
well integrated... 'gnome-vfs' is pretty much tied to everything.
So my only option appears to be one suggested by another user... remove
directory /opt and start a new install of Macports. Any other ideas?
So now "port installed dbus" should show:
---> The following versions of dbus are currently installed:
---> dbus @1.0.2_2
which means that dbus is installed but not activated. If this is the
case, try
sudo port activate dbus @1.0.2_2
(the final argument shouldn't be needed, but just to make sure), and
then try
sudo port install dbus-glib
and let us know how you go.
On the other hand, if "port installed dbus" still lists both dbus
versions (i.e. sudo port -f uninstall dbus @0.61_2 didn't work), then
you have another (and bigger) problem.
Kind regards,
Maun Suang
--Boey Maun Suang (Boey is my surname)
Email: boeyms@macports.org