Mail Archives: djgpp-workers/2001/10/10/09:28:32
Tim,
Were the tests carried out on XP home, Pro, RC1 or RC2?
Did you build the packages on XP or another Win OS?
Thanks for taking the time to do this. It's good to get this sort of
feedback as it shows that the release at clio can be used by other people to
build other major packages independantly.
> - minor packaging issues:
>
> * the timezone binaries packages contained files
> called _.CVS (ex-.cvsignore files?) - not sure
> where they came from
Charles picked these up a few days ago.
Possibly a SED issue. I am not a SED programmer and every time I look at
SED I spent 3-4 hours reading the docs to write a 10 line SED script. If
someone does know how to check / write SED scripts could they please
download the http://clio.rice.edu/djgpp/win2k/win2000_patches/distrib.zip
file and unzip it and try to run the mkdist.bat file after they modify it to
only call mkdist.bat to produce the DJGPP timezone zip file. If you do
download this ans have a look could you please let me know what the fix is.
> * the djdev package apparently contained the
> TurboVision headers, in 2 directories (there was
> both a long- and a short-named directory under
> include/).
I need to look at this, but my guess is that the find in the mkdist1.bat
file includes all header files in the include directory, but as I have
installed other packages the djdev package beocme polluted. How is it done
for a normal DJGPP release? (Built on a clean directory?)
> - good news:
>
> * running make in src/ built libc in a single run;
> no errors, no crashes, no nothing
I rebuild all of the packages from the one batch file.
> * 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))
I checked and the top level makefile I have references to _dup.c, but these
lines are commented out (start with a #). I did this so I could see what I
had modified in case I removed a file that was needed.
> * 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.
Thanks for taking the time to do this.
> - odd things (most of these are probably known issues)
I have seen some of them, but there have / are more important issues to be
solved.
> * find seems to be case sensitive even without
> FNCASE=y. Running "find -name '*.cvs'" yielded no
> results, but "find -name '*.CVS'" did.
I have added this to the list of items that need to be looked at. This is a
new issue.
> * 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)
I have added this to the list of items that need to be looked at. This is a
new issue.
> * 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.
I ran this and didn;t get a hang. The output I got was:
DJGPP_204 D:\dj204\gnu\bash-2.04>grep foo bar |less
grep: bar: No such file or directory (ENOENT)
Did I do the test correctly? I am running Win2K SP2 with a cmd.exe DOS
window.
> * The ".: /dev/null: not a regular file" during
> configure is still present.
I have added this to the list of items that need to be looked at. I have
seen this, but I have been working on more important issues.
> * 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.
I have added this to the list of items that need to be looked at. This is a
new issue.
> * 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?
Win 2K ver reports:
Microsoft Windows 2000 [Version 5.00.2195]
I am missing something as I do not see this being an issue. The LIBC has
been modified to work on Win 2K and XP.
> * 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.
I have added this to the list of items that need to be looked at. This is a
new issue.
Can't win with Bash. I can use 2.04 to build GCC, but it has issues which
have been fixed in 2.05. But 2.05 does not allow GCC to be built. In either
case the Bash read function does not work and as such I cannot rebuild Perl
with either version of bash.
Any help anyone can give with the following issues would be greatly
appreciated:
1) Bash issues - 2.04 & 2.05 read fails
- 2.05 set doesn't allow GCC to be built
2) Which crashes - use Eli's patch and release source and binary update
- update to 2.12
- normalise package add DJGPP specific readme
- send update to which maintainer
3) Check out Rhide 1.4.7.9 V's 1.4.9 (Andris V's Roberts)
4) Help out with crashes of latest RHIDE 1.4.7.9 that now "runs" under Win
2K (06-Aug-2001 release)
5) Grep configuration issue - can't rebuild using config.bat, can build
using pre-configured makefile
6) Error 183 for creating directories if exist on Win2K.
"command.com /c if not exist glob\nul md glob" returns Extended Error 183
only if directory exists (seen in makefile for mak3791 build).
Two bugs - does not see "nul" in directories, wrong error message on
create.
Using cmd.exe with same string does not generate error. Both
reproducible w/o DJGPP.
This is cosmetic W2K bug/issue - change makefile or ignore?
7) find seems to be case sensitive even without
FNCASE=y. Running "find -name '*.cvs'" yielded no
results, but "find -name '*.CVS'" did.
8) 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)
9) The ".: /dev/null: not a regular file" during
configure is still present.
10) 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.
11) 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.
(highest priority issue is #1)
- Raw text -