Date:	Tue, 3 Sep 1996 08:15:12 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Cesar Scarpini Rabak <csrabak AT dce03 DOT ipt DOT br>
Cc:	djgpp AT delorie DOT com
Subject:	Re: Compiling Emacs 19.34 package w/present ver of DJGPP
In-Reply-To:	<1.5.4.16.19960902202018.388f06cc@dmeasc.rc.ipt.br>
Message-Id:	<Pine.SUN.3.91.960903080018.24344I-100000@is>
Mime-Version:	1.0

On Mon, 2 Sep 1996, Cesar Scarpini Rabak wrote:

> So to be positive: are the two sources patches worth of putting in the libc
> until the newer version is released?

The patched versions are general and will go unaltered into the next
official library release.  The whole point in having free sources is that
you can patch your libraries/utilities without waiting for the official
release schedule (which might depend on the priorities and free time
available to the development team).  So yes, I suggest you put those
corrected versions into your library. 

> BTW, I noticed that the is_exec.c module uses several magic numbers to
> ascertain if a given file is executable; including (u**x) shell scripts. The
> question: will DJGPP programs built with this module able to run shell
> scripts calling a sh executable (namely a port of sh to MS-DOG) if
> avaialable in the machine's path?

The current version of `spawnXX' library functions can only run such
scripts if they have an extension (like `foo.sh' or `bar.sed').  Any
extension which is not .exe, .com or .bat will do, but there *has* to be
an extension.  The next release of the library will also handle
extensionless scripts.  So, in your case, rename `rcs2log' to
`rcs2log.sh', install a DOS port of a shell (`ms_sh' from SimTel), change
the `/bin/sh' path to `c:/util/sh.exe' (or whatever appropriate for your
system) and you will be able to run that script.  (However, note that I
didn't actually test this, so there might be other problems lurking in
either libc.a or Emacs code that will bite you.)

- Raw text -