Mail Archives: djgpp-workers/2001/07/27/20:35:12
Charles,
> While my time to help out on development of DJGPP is limited, I'd like to
> make sure it has a healthy future. Some of the recent traffic and
progress
> on Windows 2000 has inspired me to worry about the "Next Great Headache" -
XP.
> I've currently got XP RC1 up on a test system - with mixed results (more
> things are broken than under Windows 2000, but most of it works).
What works and what does not work?
Are the DJGPP packages stock standard from Simtel or have you re-built
them? If you have re-built them what version of CVS/LIBC are you using?
> I've rejoined the list, I've got two thoughts I'd like to get feedback on.
Excellent to see you back working with DJGPP again.
> 1) If there are some "unit tests" that I could run on XP maybe we could
> isolate some of the broken functionality. Volunteers to help set this up,
> or identify problems would be appreciated. It would be nice to be able to
> have the next major release support XP as well as Windows 2000.
The two unit test I can think of that are still on my to do list for Windows
2000 are:
1) Get make working
2) Get rhide working
Once these two unit tests are done then the other testing that needs to be
done is:
1) See if our own programs that we have written work on 2000 or XP.
2) Re-build all of the other standard GNU packages
3) Use all of the re-built GNU packages to then build some of the V2TK,
V2APP packages and see if they work.
The current info I have found in summary form is:
If you use the latest CVS 2.04 code then as far I as I have found the
following are the issues I still need to spend time investigating and
testing:
1) Make 3.791:
a) shells out to using command.com via spawnvpe function
in job.c approx line 1200 (+/- 30 lines due to debugging ) to execute
"command.com /C if not exist glob\nul md glob" then the command.com displays
an errror 183, but if I use cmd.exe then I do not get the error.
I need to check at work on NT 4.0 if the same
problem exists and if it does then see if I can produce a patch for job.c so
under Windows NT make uses cmd.exe instead of command.com. Once this is done
then I need to test it by re-building all of DJGPP and the amin GNU software
on Windows 2000 before submitting the fix as a final solution. I am thinking
to check the os_minor and os_major as is not in _open.c not NT/2000.
b) RE-built make crashes on my Win 2000 when re-building
make. Works okay in building Allegro on Win 2000. This is still WIP and I
need to re-build / test make again as per Eli's last two messages/emails.
2) Rhide 1.4.7.9 or any version - need to be re-built using the latest
CVS LIBC. So far I have not been sucessuful in doing this, I need to spend
another weekend or a few nights trying this.
Notes for Win 2000:
1) Use bash 2.0.5 as previous versions (can't remember if it was 2.0.3
or 2.0.4) has a modified low level file io which is different to the LIBC
functions which have been patched in CVS for Win 2000. Bash 2.0.5 uses the
LIBC functions.
2) Be carefull to ensure that the CVS files have the _open.c, _create.c
and NTVDM patches included in the CVS files you get. In the Make testing
still to be done may confirm that the NTVDM patch works. The other patches
are required for the DJDIR environment variable to be setup correctly in the
exe when it is run.
3) I have not been able to re-build Make on Windows 2000 so far so you
will still need another PC to build the various packages for testing on
Windows 2000.
>2) Windows 2000 and Windows XP support telnet into a console. This means
>I can potentially let certain trusted individuals to have direct access
>to a "console window" on these systems, if this would help. (I've been
>testing this over the last few days with Eli's help).
Other people may find this usefull. See responses from other people.
Reards,
Andrew
- Raw text -