Tools

TomiS said

TomiS  

Tried to install midgard2-core from macports. One problem encountered

7 comments

TomiS posted to #midgard 23.10.2009 (en)

7 comments

Bottom

TomiS  

---> Configuring midgard2-core
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_midgard2-core/work/midgard2-core-9.03.0" && ./configure --prefix=/opt/local --sysconfdir=/opt/local/etc/midgard/ --with-dbus-support " returned error 1
Command output: checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by /usr/bin/g++-4.0... /usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld
checking if the linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld) is GNU ld... no
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
checking if /usr/bin/g++-4.0 static flag -static works... no
checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin9.8.0 dyld
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking whether to use Libgda4 (libgda3 by default)... libgda-3.0
checking whether to compile dbus support (enabled by default)... yes
checking for pkg-config... /opt/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for MIDGARD... configure: error: Package requirements (glib-2.0 gobject-2.0 libxml-2.0 libgda-3.0 dbus-1 dbus-glib-1) were not met:

No package 'dbus-glib-1' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables MIDGARD_CFLAGS
and MIDGARD_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

TomiS commented on posted to #midgard 23.10.2009 (en)

TomiS  

Then I installed dbus-glib manually and after that the midgard2-core installer was able to proceed.

It just seems to me there is no package 'dbus-glib-1' available, only 'dbus-glib'

TomiS commented on posted to #midgard 23.10.2009 (en)

TomiS  

I don't know if this is relevant. Just FYI.

TomiS commented on posted to #midgard 23.10.2009 (en)

bergie  

ping @jwa

bergie commented on posted to #midgard Helsinki, Finland 23.10.2009 (en)

jwa  

@TomiS Ok, I'll have to look into that, missing dependencies are unfortunately quite normal (as I don't have a clean system to build packages in).

jwa commented on posted to #midgard 23.10.2009 (en)

tepheikk  

@jwa It's "easy" but labourfull to test. Port uninstall installed and reinstalling all takes loooong time

tepheikk commented on posted to #midgard 23.10.2009 (en)

jwa  

@TomiS @tepheikk I changed the port to depend on dbus-glib instead of dbus, dbus-glib takes care of dbus. I noticed that I had dbus-glib already installed due to some other port. Thanks for having a cleaner system than I have! (Building all ports is really an impossible task)
Binary packages are in plans, not yet in this phase, sorry, would make life a bit easier!

jwa commented on posted to #midgard 23.10.2009 (en)

Login or register to leave a comment

Publicity
These messages are public and can be seen by anyone.