<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><blockquote type="cite"><pre>On Aug 9, 2019, at 06:32, Riccardo Mottola wrote:
><i> I am re-building current GIMP on 10.5 (I have a couple of local patches to adapt it, last time they gave me a nice working app).
</i>><i>
</i>><i> Buld fails for me with:
</i>><i>
</i>><i>
</i>><i> .0 -lintl -Wl,-framework -Wl,CoreFoundation -lbabl-0.1 -ljpeg
</i>><i> libtool: link: /usr/bin/nm -p .libs/gimpmodule.o .libs/pygimp-item.o .libs/pygimp-display.o .libs/pygimp-drawable.o .libs/pygimp-image.o .libs/pygimp-parasite.o .libs/pygimp-pdb.o .libs/pygimp-tile.o .libs/pygimp-vectors.o | | /opt/local/bin/gsed 's/.* //' | sort | uniq > .libs/gimp.exp
</i>><i> ../../libtool: eval: line 1734: syntax error near unexpected token `|'
</i>><i> ../../libtool: eval: line 1734: `/usr/bin/nm -p .libs/gimpmodule.o .libs/pygimp-item.o .libs/pygimp-display.o .libs/pygimp-drawable.o .libs/pygimp-image.o .libs/pygimp-parasite.o .libs/pygimp-pdb.o .libs/pygimp-tile.o .libs/pygimp-vectors.o | | /opt/local/bin/gsed 's/.* //' | sort | uniq > .libs/gimp.exp'
</i>><i> make[4]: *** [gimp.la] Error 1
</i>><i>
</i>><i>
</i>><i> I have already seen this issue months ago, perhaps in another port, I don't remember where, the nm version used is too old and using the MacPorts one should fix it.
</i>><i>
</i>><i> How do I accomplish this? = tried setting NM on the command line but it doesn't ork.
</i>><i>
</i>><i> I guess the portfile needs a hack... and, in case, can it be done for everybody in the official portfile?
</i>
Well the obvious problem in the above output is the two pipes next to each other: "| |". That's what's causing the system error, and it wouldn't matter what version of nm you're using. There's obviously supposed to be some other program being called between those pipes, a program which perhaps is not being found on your system. I don't know what that program is; you'd have to read the build system files and see if you can find the variable that's between those two pipes and from that variable name figure out what program it's meant to be.</pre></blockquote><div>This is a rather weird error, but it indeed is caused by a too-old version of NM. Forcing a newer NM does fix it.</div><div><br></div><div>Before pounding on me about it, I didn't figure this out, so don't blame me for the seeming inconsistencies of it. Somewhere back in the ancient MacPorts tickets archives, Jeremy sorted out that when the version of NM was too old it caused this odd error. So feel free to ask him why this presents itself this way.</div><div><br></div><div>Ken</div><div><br></div><div><br></div><div><br></div></body></html>