delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/10/10/13:05:08

From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Cc: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
Subject: Re: First round of XP tests
Date: Wed, 10 Oct 2001 19:03:43 +0200
Message-ID: <000401c151ad$84f7a9e0$6ff8e0d5@pandora.be>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <005701c15183$c15ba960$0a02a8c0@acceleron>
Importance: Normal
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> Were the tests carried out on XP home, Pro, RC1 or RC2?

WinXP Pro retail (Corporate -> no activation).

> Did you build the packages on XP or another Win OS?

Packages were straight from clio.
libc, bash and emacs were all build in a 4NT prompt under XP.
I used 2 binaries from my "regular" WinME DJGPP tree: unzip.exe
to extract the packages, and m4.exe (required by autoconf).

> 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.

Happy to do it.

> 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.

If I remeber to, I'll take a look.

> 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?)

I keep my djgpp-cvs tree separate.  I think many people on
this list do this, and switch %DJGPP% depending on whether
they want stock 2.03 or bleeding-edge CVS.

> 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.

In the bsh204s.zip I downloaded yesterday, only the lines
in libdos/Makefile.in were commented out; Makefile.in still
had them (I ran configure, so maybe the lines were only
commented out in Makefile, not Makefile.in?).

> >    * emacs 21.0.97 also configured and built just fine
> Thanks for taking the time to do this.

What time? configure took about a minute; the build took 2
or 3.  Hardly a massive investment :-)

> >    * 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)

Well duh :-)
Try "grep version include/dos.h |less".

> >    * 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.

Thought it might be a way to easily distinguish 2K and XP for
the purpose of patches that are only needed on 2K.

> 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.

This is fixed in the current CVS libc; I may update libc tonight,
rebuild bash 2.04 and try to build perl.

> 1) Bash issues - 2.04 & 2.05 read fails
Fixed in CVS libc.

>                - 2.05 set doesn't allow GCC to be built
The $'foo' thing, right?  Still seems odd; bash only emits these
things in a way it can read back, so unless you mix bash versions,
there should be no problem.  May try this later.

> 5) Grep configuration issue - can't rebuild using config.bat, 
> can build using pre-configured makefile
What was the problem here? config.bat simply sets up grep for
a regular 'configure' run, doesn't it?)

>     a make install seems to create /dev/env, not /dev
>      and ./env.  This may simply be a change in the library.

This is a completely separate thing, not specific to bash at all.
Basically,
  mkdir /dev
  mkdir /dev/env
creates /dev and ./env using 2.03; with the CVS libc, you get
/dev/env (as you might expect).  I think this is simply a CVS
libc change, so probably needn't be listed here;

> 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.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019