Changes between Initial Version and Version 1 of Ticket #24477


Ignore:
Timestamp:
Apr 14, 2010, 8:05:30 AM (15 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
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.)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24477

    • Property Cc ryandesign@… added
    • Property Owner changed from macports-tickets@… to jwa@…
  • Ticket #24477 – Description

    initial v1  
    33Macbook 2.16G mid2007 10.5.8
    44
    5 I consulted this problem in a mailing list and Ryan suggested as follows:
     5I consulted this problem in a mailing list and [http://lists.macosforge.org/pipermail/macports-users/2010-April/019757.html Ryan suggested] as follows:
    66--------------------------
    77
    8 >>DEBUG: new fully merged portvariants: universal +
    9 
    10 >Ok, you're building universal.
    11 
    12 >>--->  Configuring dbus-glib for architecture ppc
    13 
    14 >>checking for BSD- or MS-compatible name lister (nm)... no
    15 
    16 >>--->  Configuring dbus-glib for architecture i386
    17 
    18 >>checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p
    19 >>checking the name lister (/usr/bin/nm -p) interface... BSD nm
    20 
    21 >And when doing the ppc part, it couldn't figure out where the "nm" command is (while for the i386 part it could).
    22 
    23 >>--->  Building dbus-glib for architecture ppc
    24 
    25 >>../libtool: eval: line 941: syntax error near unexpected token `|'
    26 
    27 >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.
    28 >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.
     8>>DEBUG: new fully merged portvariants: universal + [[br]]
     9> [[br]]
     10>Ok, you're building universal. [[br]]
     11> [[br]]
     12>>--->  Configuring dbus-glib for architecture ppc [[br]]
     13> [[br]]
     14>>checking for BSD- or MS-compatible name lister (nm)... no [[br]]
     15> [[br]]
     16>>--->  Configuring dbus-glib for architecture i386 [[br]]
     17> [[br]]
     18>>checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p [[br]]
     19>>checking the name lister (/usr/bin/nm -p) interface... BSD nm [[br]]
     20> [[br]]
     21>And when doing the ppc part, it couldn't figure out where the "nm" command is (while for the i386 part it could). [[br]]
     22> [[br]]
     23>>--->  Building dbus-glib for architecture ppc [[br]]
     24> [[br]]
     25>>../libtool: eval: line 941: syntax error near unexpected token `|' [[br]]
     26> [[br]]
     27>You'll probably find that on line 941 of the libtool, it uses the $NM variable between
     28>two pipes; since the $NM variable is empty here, that makes two pipes in a row, which
     29>is a syntax error. [[br]]
     30> [[br]]
     31>We've seen this several times before in several other ports that use the muniversal
     32>portgroup, so we just have to apply the same fix to the dbus-glib port.