From:	dje AT canuck DOT cygnus DOT com (Doug Evans)
Subject:	Re: why does /bin have to be *first* in the PATH?
5 Dec 1996 13:59:55 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199612052026.MAA19781.cygnus.gnu-win32@canuck.cygnus.com>
Original-To:	fjh AT cs DOT mu DOT OZ DOT AU
Original-CC:	gnu-win32 AT cygnus DOT com
In-reply-to:	<199612051902.GAA21191@murlibobo.cs.mu.OZ.AU> (message from
	Fergus Henderson on Fri, 6 Dec 1996 06: 02:54 +1100 (EST))
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

   From: Fergus Henderson <fjh AT cs DOT mu DOT OZ DOT AU>
   Date: Fri, 6 Dec 1996 06:02:54 +1100 (EST)

   Dear cygwin32 maintainers,

   I have programs that rely on the ability to do

	   PATH=../scripts:$PATH some_script

   This breaks in gnu-win32 version b16.

Having /bin be first in PATH was a workaround to a
bug that has since been fixed [or at least was fixed at one point].

   The following untested patch might help.

   --- spawn.cc	Thu Aug 29 12:57:46 1996
   +++ new.spawn.cc	Fri Dec  6 05:55:01 1996
   @@ -278,7 +278,7 @@
	  debug_printf ("spawn_guts: %s is a script\n", prog_arg);

	  char *sh_path_buf = (char *) alloca (MAX_PATH);
   -      char *sh_path = (char *) find_exec ("sh", sh_path_buf);
   +      char *sh_path = (char *) find_exec ("/bin/sh", sh_path_buf);
	  char *f = (char *) alloca (strlen (copy) + strlen (sh_path) + 2);
	  strcpy (f, sh_path);
	  strcat (f, " ");

I think this will require sh to be in /bin.
We're trying to get away from that.
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -