From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Fri, 29 Jun 2001 14:26:27 +0200
To:	djgpp-workers AT delorie DOT com
Subject:	Re: bash 2.04 build failure?
Message-ID:	<20010629142627.B205@lauras.lt>
Mail-Followup-To:	djgpp-workers AT delorie DOT com
References:	<3395-Wed20Jun2001200621+0300-eliz AT is DOT elta DOT co DOT il> <3B3890D8 DOT 12023 DOT 1A6E91 AT localhost> <20010628184544 DOT B205 AT lauras DOT lt>
Mime-Version:	1.0
In-Reply-To:	<20010628184544.B205@lauras.lt>
User-Agent:	Mutt/1.3.18i
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

> Consider you have hello.exe in current dir and this script:
> 
> #!/bin/sh
> if (./hello; exit) ; then
>    ac_cv_prog_cc_cross=no
> else
>    ac_cv_prog_cc_cross=yes
> fi
> echo '$ac_cv_prog_cc_cross = ' $ac_cv_prog_cc_cross
> 
> Its output:
> Hello, world!
> $ac_cv_prog_cc_cross = yes
> 
> Hello.exe returns with exit code 0.

Looks like I got it - it boils down to the same extension search order.
My testcase fails because there are both conftest and conftest.exe in same
directory. If I move out extensionless conftest outta way, it starts working.
This is a real-life example for Eli, why current libc dosexec.c is harmful
for bash.

Laurynas

- Raw text -