Message-ID:	<20010111141556.412.qmail@lauras.lt>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Thu, 11 Jan 2001 16:15:56 +0200
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	djgpp-workers AT delorie DOT com
Subject:	Re: RFC: libstdc++-v3 port
Mail-Followup-To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	djgpp-workers AT delorie DOT com
References:	<20010111124713 DOT 15142 DOT qmail AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010111150854 DOT 17787B-100000 AT is>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<Pine.SUN.3.91.1010111150854.17787B-100000@is>; from eliz@is.elta.co.il on Thu, Jan 11, 2001 at 03:10:48PM +0200
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

On Thu, Jan 11, 2001 at 03:10:48PM +0200, Eli Zaretskii wrote:
> -    /* | [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.

Laurynas

- Raw text -