Mail Archives: djgpp-workers/2001/10/10/12:48:14
> > * emacs 21.0.97 also configured and built just fine
> > (except for some lib-src/ programs that needed
> > sockets.h).
>
> That's because you didn't use config.bat to configure Emacs. The
> DJGPP port of Emacs doesn't use the configure script.
Still, that only takes a minor addition to configure.ac
and then configure works fine. I just prefer using configure
over config.bat, even if that means I need to modify configure.ac;
using a batch file just feels more hackish.
In any case, emacs builds just fine, and that was the main objective.
> There's no need: if HOME is not defined, Emacs pushes a default
> definition into the environment during startup, so HOME is always
> defined in an Emacs session. (That code goes back to when Morten
> worked on the port.)
Yes, but bash will also sometimes complain during config.status that
HOME is not set. And $DJDIR seems a natural value for HOME, unless
the user sets it differently.
> > * find seems to be case sensitive even without
> > FNCASE=y. Running "find -name '*.cvs'" yielded no
> > results, but "find -name '*.CVS'" did.
>
> What files did it find? Depending on the actual file names, this
> might or might not be expected behavior, because without FNCASE=y,
> DJGPP programs try to preserve letter-case in file names where it
> ``matters''.
find '*.cvs' returns nothing, find '*.CVS' returns the list of
'_.CVS' files in the tree.
Since the filesystem is case insensitive, name comparisons done by
find should be case insensitive as well.
Plus, the behaviour differs from WinME as well; given this tree
.
./y
./y/foo.CVS
./z
./z/z1
./z/z1/z2
./z/z1/!.CVS
./_.CVS
find '*.cvs' returns
./z/z1/!.cvs
./_.cvs
on WinME, but nothing under WinXP; find -name '*.CVS' returns
./y/foo.CVS
I can see a few cases where being so strict might be useful
(e.g. a find -name '*.S' might be intended to only return
asm-with-cpp files), but since the filesystem doesn't care, I
don't we should either.
> > * 4NT's 'ver' shows 'Windows 2000 5.01', but none of the
> > dos versions we get are 5.01 (just 5.0 and 5.50).
>
> 5.01 is the version of Windows, not the DOS version. It's the same as
> with Windows 9X: DOS version is 7.xx, but Windows versions are 4.xyz.
Right. My bad; guess I got confused because they're both 5.x.
Still, if 2K and XP return different values, that could be used to
distinguish them for W2K-only/WXP-only patches (AFAIK, currently
those simply check for 0x532).
- Raw text -