Mail Archives: djgpp-workers/2001/03/04/14:46:03
> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Sun, 4 Mar 2001 20:06:07 +0100
>
> Especially if we start to use zippo, the chance of there being a
> corrupt .elc file not introduced by the user becomes minimal.
Should I tell you how many times did I find a corrupted .elc file in
the official distribution?
> > s/msdos.h is not for this stuff, it's for system-dependent definitions
> > that usually don't change. By contrast, the list of HAVE_*
> > definitions in config.h tends to change with every release.
> Yes, but the list of functions emacs shouldn't use is probably fairly
> costant
No, it changes to track the list of functions used by Emacs for which
it probes at configure time on Unix. The reason is that I don't have
time to look at each and every library function, I do that only as
needed. You need to realize that understanding the implications of
each function is not a trivial job: I need to see how Emacs uses it
and understand where each argument comes from.
> > Doesn't this break "C-h i" if you remove INFOPATH from the environment
> > and/or DJGPP.ENV?
> Don't see how; I don't set INFOPATH anywhere
??? Did you edit DJGPP.ENV? If not, it sets INFOPATH for Emacs.
> How else would you dump emacs? Last time I checked, it didn't work
> if temacs was stubbed
That was probably a long time ago, when stubbed temacs with no .exe
extension wasn't supported.
> AFAICS, the djgpp package does the same thing (sed1x.inp changes './temacs'
> to 'go32 temacs').
sed1x.inp is not used when building with DJGPP v2, it's for the old
v1.x.
- Raw text -