Re: [Sbcl-devel] Runtime path detection

[Tobias C. R. <tc...@fr...>]

Josh Elsasser <jo...@el...> writes:

> A while back I submitted a patch to allow the runtime to fall back on
> parsing argv[0] if the OS-dependent method for finding the executable
> path fails.  More recently I revised the patch to additionally use the
> argv[0]-derived path when writing a fasl shebang line if
> os_get_runtime_executable_path() returns something which won't ever
> work, like /proc/curproc/file.
>
> I completely understand if everyone is just too busy to take the time
> to carefully read over the whole patch, I'm just trying to offer a
> gentle reminder in case it's been forgotten.
>
> In the somewhat likely case that I've explained something poorly or
> that the patch fails to take something into account, let me know what
> I can do to help.

I sent a similiar patch a while back[1]; although not as involved as
yours. Mine would just probe whether

   "$(dirname runtime_executable_path)/../lib/sbcl/"

exists, and if so, would look for the core file there.

Now reading your patch, I think your patch addresses something else in
fact; it seems like the two patches are conceptionally orthogonal to
each other (yours supplementing mine), but trying to apply them both
would probably result in conflicts.

  -T.



[1] http://sourceforge.net/mailarchive/forum.php?thread_name=873a94p6vp.fsf%40freebits.de&forum_name=sbcl-devel