Christophe Pettus <xof(at)thebuild(dot)com> writes:
> Has anyone encountered this situation (not libjvm in particular, just an external library using @rpath) during an extension build?
Yeah ... IIRC, I've hit that from trying to use the Apple-supplied
libpython to underlie PL/Python. I've not found a workaround. I suspect
that Apple doesn't want people using these OS components from "outside",
and this is something they're intentionally doing to prevent it.
IOW: I think they want you to get that from macports or homebrew instead.
It certainly works a lot easier if you do.
regards, tom lane