cygwin build_alias issue (and a possible workaround...)

[Bogdan Vacaliuc]

Hi Chris,

Thanks for that data point.  I guess there is still a deficiency.  Please try this (since it is easy for you, I think):

Add a function using the option=value items from your test-fail script into the test-configure script.  I would expect the failure
to occur on the autoconf generated configure more-or-less with the same frequency as when you call your test script.

I did this here and got this:

[/jail/cygwin-1.5.11.1-bash] ./test-configure fail_cjohns
Running using function fail_cjohns()...
*** TEST 0 ***
*** TEST 1 ***
*** TEST 1 FAILS ***
configure: error: invalid variable name: build_alias
[/jail/cygwin-1.5.11.1-bash] ./test-configure fail_cjohns
Running using function fail_cjohns()...
*** TEST 0 ***
*** TEST 1 ***
*** TEST 1 FAILS ***
configure: error: invalid variable name: build_alias
[/jail/cygwin-1.5.11.1-bash] ./test-configure fail_cjohns
Running using function fail_cjohns()...
*** TEST 0 ***
*** TEST 1 ***
*** TEST 2 ***
*** TEST 2 FAILS ***
configure: error: invalid variable name: build_alias

[NOTE: I had to remove all (3?!) references to --srcdir=, but other than that it's the same as your command line in test-fail]

I have observed sensitivity to kind and quantity of arguments as well; perhaps the build system stirs in additional entropy?  It
would be better if we could come up with a list that covers *all* machines and environments.  Clearly mine is less than that right
now.

Thanks!

-bogdan


> -----Original Message-----
> From: Chris Johns [mailto:cjohns at cybertec.com.au] 
> Sent: Monday, September 13, 2004 4:05 AM
> To: Bogdan Vacaliuc
> Cc: 'RTEMS Users'
> Subject: Re: cygwin build_alias issue (and a possible workaround...)
> 
> 
> Bogdan Vacaliuc wrote:
> > 
> > See http://cygwin.com/ml/cygwin/2004-09/msg00570.html for 
> the latest 
> > on the "build_alias" issue. There is a simplified test methodology 
> > now.
> > 
> > I must suspend my debug effort for the time being.
> > 
> 
> I am running your test-configure with a clean install of :
> 
>    MinGW-3.1.0-1.exe
>    MSYS-1.0.10.exe
>    msysDTK-1.0.1.exe
> 
> which can be downloaded from http://www.mingw.org/. This is 
> on WindowsXP 
> Pro, P4. No cygwin installed. I ran the script with cmd.exe paths to 
> MSYS and MinGW set and from a cmd.exe prompt with:
> 
>   > sh ./test-configure
> 
> The test has run 1000 times without any errors. I was also 
> able to build 
> RTEMS as M68K multilib with Cybertec Crossfire tools for RTEMS (MinGW 
> based) on XP.
> 
> Your script also works on the WinME box (not Win98 anymore) 
> passing over 
> 100 times while the original bug I posted to MinGW still occurs.
> 
> I hope this helps.
> 
> -- 
>   Chris Johns
> 
>