Date:	Mon, 2 Sep 1996 23:12:18 -0300
Message-Id:	<1.5.4.16.19960902202018.388f06cc@dmeasc.rc.ipt.br>
Mime-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	Cesar Scarpini Rabak <csrabak AT dce03 DOT ipt DOT br>
From:	Cesar Scarpini Rabak <csrabak AT dce03 DOT ipt DOT br>
Subject:	Re: Compiling Emacs 19.34 package w/present ver of DJGPP
Cc:	djgpp AT delorie DOT com

At 09:38 01/09/96 +0200, Eli Zaretskii wrote:
>
>On Fri, 30 Aug 1996, Cesar Scarpini Rabak wrote:
>
>> cd to the src sub-dir in the emacs-19.34 tree and rename the gdbinit file to
>> _gdbinit, otherwise, configure will stop and you'll need to run it again
>
>This is not as easy as it sounds.  If you use DJTAR to unzip the 
>distribution, this renaming is done automatically for you.  Otherwise, 
>the exact name of the GDB init file depends on the procedure you used to 
>unzip the .tar.gz file, and there is no way of knowing exactly how that 
>file will be called.  Therefore, CONFIG.BAT prints a message explaining 
>what you should do in case it doesn't find `_gdbinit'.  I don't know any 
>better way of doing this, but I'm open to suggestions.
>

OK! I concede that after I sent this to my friends they preferred to fetch
the binaries from my machine...
The above applies mainly to unzipping using pkunzip and winzip.

>>         gcc -O2 -g sigactio.c
>>         gcc -O2 -g is_exec.c
>> 
>> cd to the src sub-dir and issue the following:
>> 
>>         make  widgetobj='../msdos/is_exec.o ../msdos/sigactio.o'
>
>A much better way is to put the objects into your C library.  Then you 
>get the fixed versions with any other programs that you link.
>
>
I gave a thought on this when a wrote the posting, but believed that this
was only a productive suggestion if the new version of the library is not
expected to be quickly released. Also, from the comments in the two sources
I could not figure out if the corrections address a general problem (and are
considered a final solution to it) or just a topic patch while the solution
is being developed.

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

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?

This has a practical significance, since the rcs2log package (which comes
w/Emacs) would work without needing to rewrite rcs2log (now a shell script)
to be a executable (or batch file if possible, I didn't have the time still
to study that in full).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cesar Scarpini Rabak                      E-mail: csrabak AT ipt DOT br
DME/ASC                                   Phone: 55-11-268-35221Ext.350
IPT - Instituto de Pesquisas Tecnologicas Fax:   55-11-268-5996
Av. Prof. Almeida Prado, 532.  Sao Paulo - SP 05508-901 BRAZIL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- Raw text -