[MacPorts] #24477: dbus-glib will not upgrade

MacPorts noreply at macports.org
Wed Apr 14 01:05:30 PDT 2010


#24477: dbus-glib will not upgrade
-----------------------------+----------------------------------------------
 Reporter:  drnamba@…        |       Owner:  jwa@…           
     Type:  defect           |      Status:  new             
 Priority:  Normal           |   Milestone:                  
Component:  ports            |     Version:  1.8.2           
 Keywords:                   |        Port:  dbus-glib       
-----------------------------+----------------------------------------------
Changes (by ryandesign@…):

  * owner:  macports-tickets@… => jwa@…
 * cc: ryandesign@… (added)


Old description:

> I have problem in upgrading dbus-glib 0.80 to 0.86.
>
> Macbook 2.16G mid2007 10.5.8
>
> I consulted this problem in a mailing list and Ryan suggested as follows:
> --------------------------
>
> >>DEBUG: new fully merged portvariants: universal +
>
> >Ok, you're building universal.
>
> >>--->  Configuring dbus-glib for architecture ppc
>
> >>checking for BSD- or MS-compatible name lister (nm)... no
>
> >>--->  Configuring dbus-glib for architecture i386
>
> >>checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p
> >>checking the name lister (/usr/bin/nm -p) interface... BSD nm
>
> >And when doing the ppc part, it couldn't figure out where the "nm"
> command is (while for the i386 part it could).
>
> >>--->  Building dbus-glib for architecture ppc
>
> >>../libtool: eval: line 941: syntax error near unexpected token `|'
>
> >You'll probably find that on line 941 of the libtool, it uses the $NM
> variable between >two pipes; since the $NM variable is empty here, that
> makes two pipes in a row, which >is a syntax error.
> >We've seen this several times before in several other ports that use the
> muniversal >portgroup, so we just have to apply the same fix to the dbus-
> glib port.

New description:

 I have problem in upgrading dbus-glib 0.80 to 0.86.

 Macbook 2.16G mid2007 10.5.8

 I consulted this problem in a mailing list and
 [http://lists.macosforge.org/pipermail/macports-
 users/2010-April/019757.html Ryan suggested] as follows:
 --------------------------

 >>DEBUG: new fully merged portvariants: universal + [[br]]
 > [[br]]
 >Ok, you're building universal. [[br]]
 > [[br]]
 >>--->  Configuring dbus-glib for architecture ppc [[br]]
 > [[br]]
 >>checking for BSD- or MS-compatible name lister (nm)... no [[br]]
 > [[br]]
 >>--->  Configuring dbus-glib for architecture i386 [[br]]
 > [[br]]
 >>checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p
 [[br]]
 >>checking the name lister (/usr/bin/nm -p) interface... BSD nm [[br]]
 > [[br]]
 >And when doing the ppc part, it couldn't figure out where the "nm"
 command is (while for the i386 part it could). [[br]]
 > [[br]]
 >>--->  Building dbus-glib for architecture ppc [[br]]
 > [[br]]
 >>../libtool: eval: line 941: syntax error near unexpected token `|'
 [[br]]
 > [[br]]
 >You'll probably find that on line 941 of the libtool, it uses the $NM
 variable between
 >two pipes; since the $NM variable is empty here, that makes two pipes in
 a row, which
 >is a syntax error. [[br]]
 > [[br]]
 >We've seen this several times before in several other ports that use the
 muniversal
 >portgroup, so we just have to apply the same fix to the dbus-glib port.

--

Comment:

 For example, this same problem was solved in the pango port in r50606. So
 this same fix could presumably be applied to dbus-glib. (Ignore the lines
 about ac_cv_header_Carbon_Carbon_h which were specific to pango.)

-- 
Ticket URL: <http://trac.macports.org/ticket/24477#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list