Follow-up Comment #1, bug #28934 (project hurd):
btw the POSIX standard that makes me think path in execve() should always be
taken as a path (note the difference between path and file), from
http://www.opengroup.org/onlinepubs/000095399/functions/exec.html
"""
int execve(const char *path, char *const argv[], char *const envp[]);
int execlp(const char *file, const char *arg0, ... /*, (char *)0 */);
[...]
The argument path points to a pathname that identifies the new process image
file.
The argument file is used to construct a pathname that identifies the new
process image file. If the file argument contains a slash character, the file
argument shall be used as the pathname for this file. Otherwise, the path
prefix for this file is obtained by a search of the directories passed as the
environment variable PATH (see the Base Definitions volume of
IEEE Std 1003.1-2001, Chapter 8, Environment Variables). If this environment
variable is not present, the results of the search are
implementation-defined.
"""
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28934>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
