delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/10/11/08:49:01

X-Authentication-Warning: smtp3.ihug.com.au: Host p985-apx1.syd.ihug.com.au [203.173.143.223] claimed to be acceleron
Message-ID: <001b01c15252$3ef712a0$0a02a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
Cc: <djgpp-workers AT delorie DOT com>
References: <000401c151ad$84f7a9e0$6ff8e0d5 AT pandora DOT be> <006601c1523b$9514a1f0$0a02a8c0 AT acceleron> <1002799811 DOT 1295 DOT 98 DOT camel AT bender DOT falconsoft DOT be>
Subject: Re: First round of XP tests
Date: Thu, 11 Oct 2001 22:42:52 +1000
MIME-Version: 1.0
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

> > > 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
> Well, this seems _very_ unlikely, as I started from an empty dir and
> extracted packges there.  So the less and grep executables are the ones
> found in the binary packages I downloaded from clio.
I use the same exe's that get zipped up into the files at clio.

> > this doesn't fix it then I don't know what it could be. Does grep and
less
> > work standalone?
> They do.  "grep blah <file>" works, and so does 'less file'.
I don't have any other ideas.

> > The updated Bash 2.05 at clio has the read issue fixed.
>
> Good - I'll download it and see about configuring perl.
I have configured and built an updated Perl 5.6.1, but using the source from
the existing simtel sources as the ones you uploaded a few days ago to DJ's
incoming directory are still there.

In an hour or so the perl package should be available for download from
clio. I am on a 56K modem and the package is 4.4MB. I do not strip the exe
file as this would remove symbols.

> > > 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.
>
> A thought occurs - configure uses $CONFIG_SHELL (which defaults to
> $SHELL, I think) to run config.status.
> So if you run "bash205 ./configure --prefix=/dev/env/DJDIR ..." (with
> bash205.exe a bash 2.05 executable), bash 2.05 will be used for the
> configure script, but $SHELL (probably /dev/env/DJDIR/bin/bash.exe) will
> be used to run config.status.  So if $DJDIR/bin/bash.exe is bash 2.04,
> you do end up mixing versions.
I fell into this trap last night when I tested Bash 2.05, but found the
problem a few hours ago fixed it. I fixed it before I tried to build GCC. I
outlined the failure in another email ealier tonight.

> > > > 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.
>
> Oh right.  Didn't updating config.guess/config.sub help?
I will add this as a possible fix.
> I thought it was only perl's Configure that still had issues there?
The same problem also occurs with find.


> > > > 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.
> Bash 2.05 didn't have the problem, so I expect it still doesn't.
> Will try it though (might be during the weekend instead of tonight).
Ok.


- Raw text -


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