[MacPorts] #51815: librsvg @2.40.16 does not build on PPC Mac OS X 10.5.8, Leopard, because of "./libtool: eval: line 1085: syntax error near unexpected token `|' "
MacPorts
noreply at macports.org
Sat Jul 9 17:30:18 PDT 2016
#51815: librsvg @2.40.16 does not build on PPC Mac OS X 10.5.8, Leopard, because of
"./libtool: eval: line 1085: syntax error near unexpected token `|' "
------------------------------+--------------------------------
Reporter: Peter_Dyballa@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords:
Port: librsvg |
------------------------------+--------------------------------
Changes (by ryandesign@…):
* cc: jeremyhu@… (added)
Comment:
Replying to [ticket:51815 Peter_Dyballa@…]:
> but I have no idea how to test libtool, I even do not understand how the
text is output… But it's obvious that this is being evaluated:
>
> {{{
> 407 # The commands to list exported symbols.
> 408 export_symbols_cmds="\$NM \$libobjs \$convenience |
\$global_symbol_pipe | \$SED 's/.* //' | sort | uniq > \$export_symbols"
> }}}
>
> And $global_symbol_pipe is defined as:
>
> {{{
> 172 # Take the output of nm and produce a listing of raw
symbols and C names.
> 173 global_symbol_pipe=""
> }}}
>
> So defining export_symbols_cmds as
>
> {{{
> 407 # The commands to list exported symbols.
> 408 export_symbols_cmds="\$NM \$libobjs \$convenience | \$SED
's/.* //' | sort | uniq > \$export_symbols"
> }}}
>
> should work properly.
Well no. If global_symbol_pipe is empty, then the command being evaluated
is:
{{{
export_symbols_cmds="$NM $libobjs $convenience | | $SED 's/.* //' | sort |
uniq > $export_symbols"
}}}
The double pipe is what leads to the error message about the unexpected
pipe symbol. I would say it was never intended for global_symbol_pipe to
be empty, and the fact that global_symbol_pipe is empty in your case is
what needs to be fixed.
This problem was [https://lists.gnu.org/archive/html/bug-
libtool/2015-07/msg00000.html described on the libtool mailing list]
before. It seems to be a problem with nm, and that the configure script
does not exit after detecting nm's failure to parse the compiler's output.
--
Ticket URL: <https://trac.macports.org/ticket/51815#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list