Opened 6 years ago

Closed 6 years ago

#58458 closed defect (worksforme)

dbus-glib @0.110: Make build command failed

Reported by: ChrisBushman (Christopher Bushman) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: Cc:
Port: dbus-glib

Description

While attempting to install a port (Pidgin), I ran into dbus-glib as a dependency. The following is the error information I receive in dbus-glib's main.log:

:info:build /usr/bin/ld: multiple definitions of symbol _dbus_g_value_build_g_variant
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/work/dbus-glib-0.110/dbus/.libs/libdbus-glib-1.dylib(single module) definition of _dbus_g_value_build_g_variant
:info:build ./.libs/libdbus-gtool.a(dbus-gtype-specialized.o) definition of _dbus_g_value_build_g_variant in section (__TEXT,__text)
:info:build collect2: ld returned 1 exit status
:info:build make[3]: *** [Makefile:904: dbus-binding-tool] Error 1
:info:build make[3]: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/work/dbus-glib-0.110/dbus'
:info:build make[2]: *** [Makefile:1029: all-recursive] Error 1
:info:build make[2]: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/work/dbus-glib-0.110/dbus'
:info:build make[1]: *** [Makefile:524: all-recursive] Error 1
:info:build make[1]: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/work/dbus-glib-0.110'
:info:build make: *** [Makefile:424: all] Error 2
:info:build make: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/work/dbus-glib-0.110'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/work/dbus-glib-0.110" && /usr/bin/make -j2 -w all 
:info:build Exit code: 2
:error:build Failed to build dbus-glib: command execution failed
:debug:build Error code: CHILDSTATUS 15542 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_dbus-glib/dbus-glib/main.log for details.

Attached is the full main.log and config.log.

Attachments (2)

main.log (531.3 KB) - added by ChrisBushman (Christopher Bushman) 6 years ago.
Main.log of build output for dbus-glib
config.log (39.9 KB) - added by ChrisBushman (Christopher Bushman) 6 years ago.
Config.log of dbus-glib-0.110

Download all attachments as: .zip

Change History (7)

Changed 6 years ago by ChrisBushman (Christopher Bushman)

Attachment: main.log added

Main.log of build output for dbus-glib

Changed 6 years ago by ChrisBushman (Christopher Bushman)

Attachment: config.log added

Config.log of dbus-glib-0.110

comment:1 Changed 6 years ago by kencu (Ken)

between attempts to build, you always need to clean up the previous build, like so:

sudo port clean dbus-glib

can you please give me the output of

port -v installed | grep gcc
port -v installed | grep cctools
port -v installed | grep ld64

Thanks.

comment:2 Changed 6 years ago by kencu (Ken)

Looks like it does install on Tiger:

$ port -v installed dbus-glib
The following ports are currently installed:
  dbus-glib @0.108_0 platform='darwin 8' archs='ppc' date='2017-04-01T20:28:15-0700'
  dbus-glib @0.110_0 (active) platform='darwin 8' archs='ppc' date='2018-04-14T12:19:08-0700'

comment:3 Changed 6 years ago by ChrisBushman (Christopher Bushman)

It appears I did not have cctools set up on my system. After installing cctools and verifying gcc and ld64 were setup, the installation executed successfully. Thank you for the help kencu.

comment:4 Changed 6 years ago by kencu (Ken)

that's great! Not 100% sure how our nets let you not have cctools installed, but I guess there are always a few cracks in the armour...

comment:5 Changed 6 years ago by kencu (Ken)

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.