[Openmcl-devel] CCL startup script (ccl & ccl64) is not Bourne Shell compatible
Tim Bradshaw
tfb at tfeb.org
Wed Oct 28 14:44:07 PDT 2009
On 28 Oct 2009, at 21:13, Aleksej Saushev wrote:
> Well... If you don't know your target system, you may be unpleasantly
> surprised at some point. That's with usage of both "#!/usr/bin/env"
> and
> LD_LIBRARY_PATH.
Indeed. The aim is to get as few surprises as possible while ensuring
stuff works with as little hassle as possible, and you have a chance
in hell of getting it through audit.
> The main difference from Lisp is that you (as a sysadmin) have
> control on
> both interpreter and RPATH, you can change them in-place (except in
> some
> extremely paranoid cases, where you run security-hardened site with
> executable protection and such).
I vaguely remember sites like that, nice to know they still exist.
More information about the Openmcl-devel
mailing list