X-Authentication-Warning: new-smtp1.ihug.com.au: Host p335-tnt2.syd.ihug.com.au [203.173.131.81] claimed to be acceleron Message-ID: <006601c1523b$9514a1f0$0a02a8c0@acceleron> From: "Andrew Cottrell" To: "Tim Van Holder" , References: <000401c151ad$84f7a9e0$6ff8e0d5 AT pandora DOT be> Subject: Re: First round of XP tests Date: Thu, 11 Oct 2001 20:00:37 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Reply-To: djgpp-workers AT delorie DOT com > 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). I just updated Bash 2.05 to the 08-Oct-2001 source. > > 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. Unfortunatly I have been on the bleeding edge CVS tree since about July. Call me crazy, and sometimes I do make mistakes because of the loss of blood. > > 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?). I didn't think about makefile.in. I have updated the sources at clio. > > > * 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". I tried this and it worked. The output I got was: DJGPP_204 D:\dj204>grep version include/dos.h |less extern unsigned short _os_trueversion; unsigned short _get_dos_version(int); I suspect an old exe in the bin directory. Check to see that the exe file dates are from this month and if not then unzip the binary package again. If this doesn't fix it then I don't knwo what it could be. Does grep and less work standalone? > > 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. The updated Bash 2.05 at clio has the read issue fixed. > > - 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. Yes this is the issue. I am now comparing Bash 2.04 and 2.05 output from GCC build to see if it is fixed, but preliminary test failed and I am testing again just in case. > > 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?) It can't guess the host type. > > 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; Shouldn't the creation of these be surpressed? > > 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. Could you try again with the updated Bash 2.05 from clio and let me know how you get on.