Opened 14 years ago

Closed 13 years ago

#25581 closed defect (fixed)

dbus-glib +universal build failed

Reported by: hvdwolf@… Owned by: jyrkiwahlstedt
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: dbus-glib

Description (last modified by mf2k (Frank Schima))

After updating to 1.91 from 1.81 I tried to update dbus-glib (this version now 0.86). It ends in an error.

shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus-glib/work/dbus-glib-0.86-ppc" && /usr/bin/make all " returned error 2
:error:build Target org.macports.build returned: shell command failed

I uninstalled both dbus and dbus-glib and tried to install dbus-glib again but with the same error. Please find attached the main.log from the build process.

Attachments (2)

main.log (71.1 KB) - added by hvdwolf@… 14 years ago.
logfile of install process
dbus-glib-Portfile.diff (556 bytes) - added by hvdwolf@… 14 years ago.
unified diff for the Portfile

Download all attachments as: .zip

Change History (9)

Changed 14 years ago by hvdwolf@…

Attachment: main.log added

logfile of install process

comment:1 Changed 14 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to jwa@…
Summary: dbus-glib: shell command faileddbus-glib +universal build failed

Please remember to cc the maintainer.

comment:2 Changed 14 years ago by mf2k (Frank Schima)

Description: modified (diff)

comment:3 Changed 14 years ago by jyrkiwahlstedt

Unfortunately I don't have a ppc system available (you seem to have 10.5 level system)...

comment:4 Changed 14 years ago by hvdwolf@…

I have a 10.5.8 Intel core duo MacbookPro system and I don't have a ppc system either. If I do a "sudo port install dbus-glib -universal" it works. The previous 0.76_0 wasn't universal either. I could only build it as i386. Now that the 0.86_1 "fails" again I wanted to register it as an error. Is there more I can test?

comment:5 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

This is probably the relatively common "can't find nm when building for the other architecture" problem we've had and fixed with several ports already over the years.

:info:configure --->  Configuring dbus-glib for architecture i386
--
:info:configure checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p
:info:configure checking the name lister (/usr/bin/nm -p) interface... BSD nm
--
:info:configure checking command to parse /usr/bin/nm -p output from /usr/bin/gcc-4.0 object... ok
--
:info:configure --->  Configuring dbus-glib for architecture ppc
--
:info:configure checking for BSD- or MS-compatible name lister (nm)... no
--
:info:configure checking the name lister (link -dump -symbols) interface... BSD nm

Could possibly be fixed like it was for pango in r50606 for example.

Why do you want to build ppc/i386 universal anyway?

comment:6 Changed 14 years ago by hvdwolf@…

That solution does work. I attached a unified diff for the Portfile.

I want to build universal as I'm the bundle maintainer for avidemux. I create a universal (Snow)Leopard bundle. dbus-glib is not part of that but simply one of the underlying dependencies for the entire process.

Changed 14 years ago by hvdwolf@…

Attachment: dbus-glib-Portfile.diff added

unified diff for the Portfile

comment:7 Changed 13 years ago by jmroot (Joshua Root)

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