MacPorts, X11 and /opt/local/lib clashing libraries

[Greg Earle]

Different topic:

Our software is currently Solaris and Linux-based with an X Windows
component (some of which uses OpenMotif).  We have a prototype Mac
port built by the lead developer and he installed OpenMotif directly
from the source (www.ist-inc.com) into "/usr/OpenMotif".

Does anyone use MacPorts for X11 stuff?  I would prefer to use
MacPorts, but it looks to me like if I install the "openmotif"
port ,it sucks in all sorts of other dependent X11 ports and to
be honest given that Apple has "blessed" XQuartz 2.7.4 I would
prefer to be compiling/linking against the XQuartz stuff instead.

I'm also wary of things like getting an updated "libiconv" in the
bargain and having that get sucked in first (via $LD_LIBRARY_PATH
perhaps) causing it to blow up our build scripts up because "tcsh"
(don't ask!) needs the system "libiconv", and it can't have the
MacPorts-installed one ahead of it in the library search path.

	- Greg