Date: Sun, 8 Aug 1999 14:46:55 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>,
        DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: Bug and patch for GDB's aclocal.m4
In-Reply-To: <37A9DBA0.4546E3B5@softhome.net>
Message-ID: <Pine.SUN.3.91.990808144639.23423t-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 5 Aug 1999, Laurynas Biveinis wrote:

> Note that the check above accepts only backslashes, but
> gcc prints program path with forward slashes. So I fixed
> this by changing line above to
> /* | [A-Za-z]:[\\/]*)

This is the right patch.

> I patched configures and aclocal.m4s but aren't aclocal.m4
> generated somewhere else?

Yes, they are usually generated by the ACLOCAL script.  You should be
able to see that on the first line of aclocal.m4.

> In that case the actual bug 
> is there, but I couldn't find it.

I think it comes from libtool (see ltmain.sh and ltconfig).

> Now that configure test succeeds, but I'm still unable 
> to build GDB :(

I did succeed to build it, both on Windows 9X and in plain DOS.  This
was an alpha version that Robert released a while ago (didn't yet have
time to try the final release), but I doubt that the differences are
significant.  So perhaps you could describe the failure (error
message(s), the fragment of the script that fails, etc.), and we will
try to help.