Subject: First round of XP tests
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: djgpp-workers AT delorie DOT com
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.15.99+cvs.2001.10.05.05.19 (Preview Release)
Date: 10 Oct 2001 08:32:59 +0200
Message-Id: <1002695580.4725.19.camel@bender.falconsoft.be>
Mime-Version: 1.0
Reply-To: djgpp-workers AT delorie DOT com

Here are the results of the Belgian jury:

 - minor packaging issues:

   * the timezone binaries packages contained files
     called _.CVS (ex-.cvsignore files?) - not sure
     where they came from
   * the djdev package apparently contained the
     TurboVision headers, in 2 directories (there was
     both a long- and a short-named directory under
     include/).

 - good news:

   * running make in src/ built libc in a single run;
     no errors, no crashes, no nothing
   * bash 2.04 also configured (using a configure
     script generated by autoconf 2.52) and built OK
     (though the top-level makefile still referenced
     sources that are no longer used by libdos
     (_dup.c etc))
   * emacs 21.0.97 also configured and built just fine
     (except for some lib-src/ programs that needed
     sockets.h).  It seems to run fine (including menus),
     though it load my _emacs.
     Note: like some other programs, emacs wants $HOME
     to be set.  Maybe djgpp.env should have a global
       HOME=+%DJDIR%
     or something.

 - odd things (most of these are probably known issues)

   * find seems to be case sensitive even without
     FNCASE=y. Running "find -name '*.cvs'" yielded no
     results, but "find -name '*.CVS'" did.
   * less has problems with input.  Enhanced keys don't
     work, and text input (eg when searching) is shown
     double (eg a search for foo shows '/ffoooo' in the
     status line)
   * grep foo bar |less does not work (hangs the prompt)
     I expect this is still the 'no seeks on stdin' issue?
     This does work under bash.
   * The ".: /dev/null: not a regular file" during
     configure is still present.
   * bash (both versions) seems to expand /dev/env paths
     more than necessary; configure prints
       loading site script d:/djgpp/share/config.site
     instead of
       loading site script /dev/env/DJDIR/share/config.site
     This is probably harmless, but may cause problems;
     one of the good things about /dev/env paths is that
     there is no drivespec to cause colon issues.
   * a make install seems to create /dev/env, not /dev
     and ./env.  This may simply be a change in the library.
   * 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).
     Not sure what W2K reports.  Maybe we could use a VXD
     call under windows to get the version it reports to
     32-bit apps?
   * bash 2.04 is unable to run autoconf; m4 complains
       d:djgpptmp/t1234.567/traces.m4: no such file ...
     Apparently, it somehow gets a path with backslashes.
     bash 2.05 does not have this problem.