On Fri, 2017-09-08 at 00:39 +0200, Samuel Thibault wrote:
> That goes back to file_exec_file_name provided with a relative path, and not
> an
> absolute path. That's where it needs fixing. I guess it could be a
> matter of making sysdeps/mach/hurd/execve.c call realpath(), as well as
> sysdeps/m
Svante Signell, on sam. 09 sept. 2017 10:51:36 +0200, wrote:
> On Fri, 2017-09-08 at 00:39 +0200, Samuel Thibault wrote:
> > That goes back to file_exec_file_name provided with a relative path, and not
> > an
> > absolute path. That's where it needs fixing. I guess it could be a
> > matter of mak
