#36502: emacs-app: hardcoded build path -------------------------------------+---------------------- Reporter: mojca.miklavec.lists@… | Owner: hum@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: emacs-app | -------------------------------------+---------------------- Comment (by mojca.miklavec.lists@…): Replying to [comment:3 jrh@…]:
Replying to [comment:2 hum@…]:
Emacs.app is relocatable while /opt/local/bin/emacs is not, and you should not separate the Emacs binary from other data files, because the binary could not find them based on the relative paths.
OK, so you're saying that Emacs.app is set up to search within its (relocatable) app bundle, and so the symlink fails because it's looking for stuff at {{{`dirname argv[0]`/libexec/}}} and {{{`dirname argv[0]`/../Resources/}}} (pardon the syntax abuse). That makes sense, and I suppose it means this bug is really a feature.
TeX is also relocatable and uses SELFAUTOPARENT (../) to find texmf.cnf, but one can use an arbitrary number of symlinks. It just works - the files are searched relative from the executable not relative to the symlinks. So even if that's the case it is still very suboptimal behaviour. And I don't like the fact that it complains about files missing in the original building directory -- Ticket URL: <https://trac.macports.org/ticket/36502#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS