From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	<djgpp-workers AT delorie DOT com>
Subject:	RE: RFC: libstdc++-v3 port
Date:	Thu, 11 Jan 2001 21:58:49 +0100
Message-ID:	<NEBBIOJNGMKPNOBKHCGHCEIFCAAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To:	<20010111141556.412.qmail@lauras.lt>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id PAA27581
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

> > -    /* | [A-Za-z]:[/\\]*) libgcj_flagbasedir=[$]{glibcpp_basedir} ;;
> > +    /* | [A-Za-z]:[\\/]*) libgcj_flagbasedir=[$]{glibcpp_basedir} ;;
> I'm told by Alexandre Oliva that [/\\] sequence triggers a bug
> in some versions of bash.
Yes - bash doesn't match a backslash if [/\\] is used (although it should).
autoconf already uses [\\/] all over the place; but some aclocal stuff
doesn't, unfortunately.

- Raw text -