X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Rugxulo <rugxulo AT gmail DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: problems with gnu configure on djgpp
Date:	Wed, 15 Jul 2009 04:35:14 -0700 (PDT)
Organization:	http://groups.google.com
Lines:	25
Message-ID:	<b4f9dd24-e778-4045-9202-d7a75686bd50@y7g2000yqa.googlegroups.com>
References:	<508a729d-3b21-4140-8da0-c2061e93c559 AT p21g2000prn DOT googlegroups DOT com>
	<E1MFJkN-0007TS-Bi AT fencepost DOT gnu DOT org> <a2bad516-68b0-4f4b-b40a-2a840131050c AT k26g2000vbp DOT googlegroups DOT com>
	<83r5wkq883 DOT fsf AT gnu DOT org>
NNTP-Posting-Host:	65.13.115.246
Mime-Version:	1.0
X-Trace:	posting.google.com 1247657714 3700 127.0.0.1 (15 Jul 2009 11:35:14 GMT)
X-Complaints-To:	groups-abuse AT google DOT com
NNTP-Posting-Date:	Wed, 15 Jul 2009 11:35:14 +0000 (UTC)
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	y7g2000yqa.googlegroups.com; posting-host=65.13.115.246;
	posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent:	G2/1.0
X-HTTP-UserAgent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US)
	AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.33 Safari/530.5,gzip(gfe),gzip(gfe)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,

On Jul 13, 10:00=A0pm, Eli Zaretskii <e DOT  DOT  DOT  AT gnu DOT org> wrote:
> > From: Rugxulo <rugx DOT  DOT  DOT  AT gmail DOT com>
> > Date: Mon, 13 Jul 2009 14:31:16 -0700 (PDT)
>
> > > > bash-2.04$ ./configure
> > > > configure: loading site script c:/djgpp/share/config.site
> > > > configure: loading cache /dev/null
> > > > ./configure: .: /dev/null: not a regular file
>
> > > What OS is that? =A0Also, what line in the configure script triggers
> > > this error message?
>
> > I think this is Bash 2.04 that has this issue. If you use 2.05 (from /
> > beta/) at least some of these warnings go away. I don't know for sure
> > why offhand, though.
>
> FWIW, I use Bash 2.04r2, and I don't have these problems (on Windows
> XP).

Perhaps you are using a newer or modified config.site? Surely that
would fix at least some problems. To be honest, I wonder if some of
the configure errors are due to blind assumptions of script writers
assuming newer Bash versions.

- Raw text -