Gnucash fails to install: configure dbus-glib failure
Sorry, first post was in html. Here's the trace in plain text (I hope!) Any suggestions? Bj IBook:~ bj$ sudo port install gnucash ---> Configuring dbus-glib 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_devel_dbus-glib/work/dbus-glib-0.73" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man --enable-tests " returned error 1 Command output: checking for sys/uio.h... yes checking for writev... yes checking for ISO C99 varargs macros in C... yes checking for GNUC varargs macros... yes checking for struct cmsgcred... no checking for getpeerucred... yes checking for getpeereid... yes checking abstract socket namespace... no checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /opt/local/bin/msgfmt checking for dcgettext... yes checking for gmsgfmt... /opt/local/bin/msgfmt checking for xgettext... /opt/local/bin/xgettext ./configure: line 27823: ./po/POTFILES.in: No such file or directory checking for XML_ParserCreate_MM in -lexpat... yes checking expat.h usability... yes checking expat.h presence... yes checking for expat.h... yes checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for DBUS... configure: error: DBus development libraries not found Error: The following dependencies failed to build: libgtkhtml312 dbus-glib p5-finance-quote p5-crypt-ssleay p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base p5-io-compress-zlib p5-html-parser p5-html-tagset p5-uri p5-datemanip p5-html-tableextract Error: Status 1 encountered during processing.
On Apr 22, 2007, at 00:16, Bjorn Berg wrote:
---> Configuring dbus-glib [snip] checking for DBUS... configure: error: DBus development libraries not found
So you're trying to install dbus-glib, and it can't find the dbus libraries. I imagine this would be fixed by installing the dbus port first. Please try that and let us know if that fixes it. Then we can add that as a dependency to the dbus-glib port so that this situation is handled automatically in the future.
On Apr 22, 2007, at 01:43, Ryan Schmidt wrote:
On Apr 22, 2007, at 00:16, Bjorn Berg wrote:
---> Configuring dbus-glib [snip] checking for DBUS... configure: error: DBus development libraries not found
So you're trying to install dbus-glib, and it can't find the dbus libraries. I imagine this would be fixed by installing the dbus port first. Please try that and let us know if that fixes it. Then we can add that as a dependency to the dbus-glib port so that this situation is handled automatically in the future.
Um... Sorry, I see that dbus-glib already declares dbus as a dependency. So is dbus installed?
I checked for dbus. It's invoked on my command line to start GNOME. So a ran a search and an install and got this trace: port search dbus dbus devel/dbus 1.0.2 A message bus system, a simple way for applications to talk to one another. dbus-glib devel/dbus-glib 0.73 Glib bindings for the dbus message bus system. IBook:~ bj$ sudo port install dbus ---> Activating dbus 1.0.2_2 Error: Target com.apple.activate returned: Image error: Another version of dbus (0.61_2) is already active. Error: Status 1 encountered during processing. If I uninstall the older version what flaky behaviour can I expect trying to install the new one? Bj Ryan Schmidt wrote:
On Apr 22, 2007, at 01:43, Ryan Schmidt wrote:
On Apr 22, 2007, at 00:16, Bjorn Berg wrote:
---> Configuring dbus-glib [snip] checking for DBUS... configure: error: DBus development libraries not found
So you're trying to install dbus-glib, and it can't find the dbus libraries. I imagine this would be fixed by installing the dbus port first. Please try that and let us know if that fixes it. Then we can add that as a dependency to the dbus-glib port so that this situation is handled automatically in the future.
Um... Sorry, I see that dbus-glib already declares dbus as a dependency.
So is dbus installed?
Uninstalling the old version and installing the new version is recommended. However, some programs that were bound against the old version may nor run correctly. These programs should then be rebuilt. On 22 Apr 2007, at 11:03, Bjorn Berg wrote:
I checked for dbus. It's invoked on my command line to start GNOME. So a ran a search and an install and got this trace:
port search dbus dbus devel/dbus 1.0.2 A message bus system, a simple way for applications to talk to one another. dbus-glib devel/dbus-glib 0.73 Glib bindings for the dbus message bus system. IBook:~ bj$ sudo port install dbus ---> Activating dbus 1.0.2_2 Error: Target com.apple.activate returned: Image error: Another version of dbus (0.61_2) is already active. Error: Status 1 encountered during processing.
If I uninstall the older version what flaky behaviour can I expect trying to install the new one?
Bj
Ryan Schmidt wrote:
On Apr 22, 2007, at 01:43, Ryan Schmidt wrote:
On Apr 22, 2007, at 00:16, Bjorn Berg wrote:
---> Configuring dbus-glib [snip] checking for DBUS... configure: error: DBus development libraries not found
So you're trying to install dbus-glib, and it can't find the dbus libraries. I imagine this would be fixed by installing the dbus port first. Please try that and let us know if that fixes it. Then we can add that as a dependency to the dbus-glib port so that this situation is handled automatically in the future.
Um... Sorry, I see that dbus-glib already declares dbus as a dependency.
So is dbus installed?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
So I'm new at this. Can I just type 'port uninstall dbus' on a command line? How do I find those programs that are affected by the newinstall, just run everything? Shouldn't this be a consideration in the release of a new version that looks like its capable of so much havoc? Bj Randall Wood wrote:
Uninstalling the old version and installing the new version is recommended. However, some programs that were bound against the old version may nor run correctly. These programs should then be rebuilt.
On 22 Apr 2007, at 11:03, Bjorn Berg wrote:
I checked for dbus. It's invoked on my command line to start GNOME. So a ran a search and an install and got this trace:
port search dbus dbus devel/dbus 1.0.2 A message bus system, a simple way for applications to talk to one another. dbus-glib devel/dbus-glib 0.73 Glib bindings for the dbus message bus system. IBook:~ bj$ sudo port install dbus ---> Activating dbus 1.0.2_2 Error: Target com.apple.activate returned: Image error: Another version of dbus (0.61_2) is already active. Error: Status 1 encountered during processing.
If I uninstall the older version what flaky behaviour can I expect trying to install the new one?
Bj
Ryan Schmidt wrote:
On Apr 22, 2007, at 01:43, Ryan Schmidt wrote:
On Apr 22, 2007, at 00:16, Bjorn Berg wrote:
---> Configuring dbus-glib [snip] checking for DBUS... configure: error: DBus development libraries not found
So you're trying to install dbus-glib, and it can't find the dbus libraries. I imagine this would be fixed by installing the dbus port first. Please try that and let us know if that fixes it. Then we can add that as a dependency to the dbus-glib port so that this situation is handled automatically in the future.
Um... Sorry, I see that dbus-glib already declares dbus as a dependency.
So is dbus installed?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com
"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
A simple "sudo port selfupdate ; sudo port outdated" should take care of uninstalling and reinstalling most outdated versions of software that depended on the older version of dbus. Note that dbus version 0.61 was a development version with an unstable API while dbus version 1.x.y has a stable API and it is a good idea therefore to make sure everything works with the new version. On 22 Apr 2007, at 12:13, Bjorn Berg wrote:
So I'm new at this. Can I just type 'port uninstall dbus' on a command line? How do I find those programs that are affected by the newinstall, just run everything? Shouldn't this be a consideration in the release of a new version that looks like its capable of so much havoc?
Bj
Randall Wood wrote:
Uninstalling the old version and installing the new version is recommended. However, some programs that were bound against the old version may nor run correctly. These programs should then be rebuilt.
On 22 Apr 2007, at 11:03, Bjorn Berg wrote:
I checked for dbus. It's invoked on my command line to start GNOME. So a ran a search and an install and got this trace:
port search dbus dbus devel/dbus 1.0.2 A message bus system, a simple way for applications to talk to one another. dbus-glib devel/dbus-glib 0.73 Glib bindings for the dbus message bus system. IBook:~ bj$ sudo port install dbus ---> Activating dbus 1.0.2_2 Error: Target com.apple.activate returned: Image error: Another version of dbus (0.61_2) is already active. Error: Status 1 encountered during processing.
If I uninstall the older version what flaky behaviour can I expect trying to install the new one?
Bj
Ryan Schmidt wrote:
On Apr 22, 2007, at 01:43, Ryan Schmidt wrote:
On Apr 22, 2007, at 00:16, Bjorn Berg wrote:
---> Configuring dbus-glib [snip] checking for DBUS... configure: error: DBus development libraries not found
So you're trying to install dbus-glib, and it can't find the dbus libraries. I imagine this would be fixed by installing the dbus port first. Please try that and let us know if that fixes it. Then we can add that as a dependency to the dbus-glib port so that this situation is handled automatically in the future.
Um... Sorry, I see that dbus-glib already declares dbus as a dependency.
So is dbus installed?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com
"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
On Apr 22, 2007, at 12:41, Randall Wood wrote:
On 22 Apr 2007, at 12:13, Bjorn Berg wrote:
So I'm new at this. Can I just type 'port uninstall dbus' on a command line? How do I find those programs that are affected by the newinstall, just run everything? Shouldn't this be a consideration in the release of a new version that looks like its capable of so much havoc?
A simple "sudo port selfupdate ; sudo port outdated" should take care of uninstalling and reinstalling most outdated versions of software that depended on the older version of dbus.
a) No, it won't: "sudo port outdated" will only show a list of ports that are outdated; it will not update them. b) That wasn't the question. The question was, once dbus has been upgraded, if it is an ABI-incompatible upgrade, how does one identify all ports that depend on dbus (whether or not they are outdated) so that they can be rebuilt? The answer is the the depsearch script in the wiki: http://trac.macosforge.org/projects/macports/wiki/ ProblemHotlist#a2.Aportfailedtobuildupgradeorrunwithamessagereferringtol ibintl.3.dylib Bjorn: sorry, MacPorts isn't smart enough to do this on its own. The port system does not track whether an upgrade is ABI-compatible or not. It just knows whether there is an upgrade to a port. It's up to you to confirm that everything still works after upgrading a port, and rebuild any dependencies as needed. The depsearch script above can help you identify what you need to do. You will, by the way, need "sudo port -f uninstall dbus", since otherwise MacPorts will complain that some other port depends on dbus. This may also be a way to determine which ports you need to rebuild, though I do not know if this will be the same list returned by depsearch.
On 22 Apr 2007, at 18:11, Ryan Schmidt wrote:
On Apr 22, 2007, at 12:41, Randall Wood wrote:
On 22 Apr 2007, at 12:13, Bjorn Berg wrote:
So I'm new at this. Can I just type 'port uninstall dbus' on a command line? How do I find those programs that are affected by the newinstall, just run everything? Shouldn't this be a consideration in the release of a new version that looks like its capable of so much havoc?
A simple "sudo port selfupdate ; sudo port outdated" should take care of uninstalling and reinstalling most outdated versions of software that depended on the older version of dbus.
a) No, it won't: "sudo port outdated" will only show a list of ports that are outdated; it will not update them.
Sorry. That should read "sudo port upgrade outdated"
b) That wasn't the question. The question was, once dbus has been upgraded, if it is an ABI-incompatible upgrade, how does one identify all ports that depend on dbus (whether or not they are outdated) so that they can be rebuilt? The answer is the the depsearch script in the wiki:
http://trac.macosforge.org/projects/macports/wiki/ ProblemHotlist#a2.Aportfailedtobuildupgradeorrunwithamessagereferringt olibintl.3.dylib
Bjorn: sorry, MacPorts isn't smart enough to do this on its own. The port system does not track whether an upgrade is ABI-compatible or not. It just knows whether there is an upgrade to a port. It's up to you to confirm that everything still works after upgrading a port, and rebuild any dependencies as needed. The depsearch script above can help you identify what you need to do.
You will, by the way, need "sudo port -f uninstall dbus", since otherwise MacPorts will complain that some other port depends on dbus. This may also be a way to determine which ports you need to rebuild, though I do not know if this will be the same list returned by depsearch.
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
Yep I tried the "sudo port upgrade outdated" and after 3 hours of minor upgrades things fell apart, especially with gnome and lib... packages. The install would hang on > configuring dbus-lib... and give me an error. After it called dbus for the fourth time I shut it down. Curiously when I rebooted my terminal prompt was preceded by "-bash: no job control in this shell". Oh well, if its fritzed we'll go back to Windows. But I'm not giving up yet. I like the suggestion of "sudo port -f uninstall dbus" So if the thing isn't totally fritzed I'm going to do that and if it works, I'll try uninstalling dbus-lib, too. Then I'll try installing them "sudo port install dbus", followed by another round of "sudo port upgrade outdated" for all those ports that failed to upgrade because of the out-of-date version of dbus. Let's see, should be done by Friday I would think!!! Bj Randall Wood wrote:
On 22 Apr 2007, at 18:11, Ryan Schmidt wrote:
On Apr 22, 2007, at 12:41, Randall Wood wrote:
On 22 Apr 2007, at 12:13, Bjorn Berg wrote:
So I'm new at this. Can I just type 'port uninstall dbus' on a command line? How do I find those programs that are affected by the newinstall, just run everything? Shouldn't this be a consideration in the release of a new version that looks like its capable of so much havoc?
A simple "sudo port selfupdate ; sudo port outdated" should take care of uninstalling and reinstalling most outdated versions of software that depended on the older version of dbus.
a) No, it won't: "sudo port outdated" will only show a list of ports that are outdated; it will not update them.
Sorry. That should read "sudo port upgrade outdated"
b) That wasn't the question. The question was, once dbus has been upgraded, if it is an ABI-incompatible upgrade, how does one identify all ports that depend on dbus (whether or not they are outdated) so that they can be rebuilt? The answer is the the depsearch script in the wiki:
http://trac.macosforge.org/projects/macports/wiki/ProblemHotlist#a2.Aportfai...
Bjorn: sorry, MacPorts isn't smart enough to do this on its own. The port system does not track whether an upgrade is ABI-compatible or not. It just knows whether there is an upgrade to a port. It's up to you to confirm that everything still works after upgrading a port, and rebuild any dependencies as needed. The depsearch script above can help you identify what you need to do.
You will, by the way, need "sudo port -f uninstall dbus", since otherwise MacPorts will complain that some other port depends on dbus. This may also be a way to determine which ports you need to rebuild, though I do not know if this will be the same list returned by depsearch.
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com
"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
I just decided to blow away my 1.3.x installation and start from scratch. I ran into a bunch of issues building qt3, which I'd run into before, and which I'd hacked to get working. Doing a port selfupdate moved me up to 1.43, but trying to upgrade gnucash was a disaster. Started over from a blank slate, and everything installed just fine (yes, after a few hours). -Fred On Apr 22, 2007, at 6:57 PM, Bjorn Berg wrote:
Let's see, should be done by Friday I would think!!!
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? I'm going to finish watching the hockey game and go to bed. Bj Randall Wood wrote:
On 22 Apr 2007, at 18:11, Ryan Schmidt wrote:
On Apr 22, 2007, at 12:41, Randall Wood wrote:
On 22 Apr 2007, at 12:13, Bjorn Berg wrote:
So I'm new at this. Can I just type 'port uninstall dbus' on a command line? How do I find those programs that are affected by the newinstall, just run everything? Shouldn't this be a consideration in the release of a new version that looks like its capable of so much havoc?
A simple "sudo port selfupdate ; sudo port outdated" should take care of uninstalling and reinstalling most outdated versions of software that depended on the older version of dbus.
a) No, it won't: "sudo port outdated" will only show a list of ports that are outdated; it will not update them.
Sorry. That should read "sudo port upgrade outdated"
b) That wasn't the question. The question was, once dbus has been upgraded, if it is an ABI-incompatible upgrade, how does one identify all ports that depend on dbus (whether or not they are outdated) so that they can be rebuilt? The answer is the the depsearch script in the wiki:
http://trac.macosforge.org/projects/macports/wiki/ProblemHotlist#a2.Aportfai...
Bjorn: sorry, MacPorts isn't smart enough to do this on its own. The port system does not track whether an upgrade is ABI-compatible or not. It just knows whether there is an upgrade to a port. It's up to you to confirm that everything still works after upgrading a port, and rebuild any dependencies as needed. The depsearch script above can help you identify what you need to do.
You will, by the way, need "sudo port -f uninstall dbus", since otherwise MacPorts will complain that some other port depends on dbus. This may also be a way to determine which ports you need to rebuild, though I do not know if this will be the same list returned by depsearch.
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com
"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
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
There appears to be a conflict between different versions of guile and slib. These are the versions and status of the ones installed on my system. I think gnucash is making a conflicting call on these files.
g-wrap16 @1.3.4_4 (active) guile @1.6.8_0+darwin_8 guile @1.8.1_1+darwin_8 (active) guile16 @1.6.8_0+darwin_8
This problem is described here: http://wiki.gnucash.org/wiki/MacOSXInstallation#guile_1.8.1 Could you follow the instructions given there and report back again? Regards, Marc
participants (6)
-
Bjorn Berg
-
Boey Maun Suang
-
Fred Dushin
-
Marc André Selig
-
Randall Wood
-
Ryan Schmidt