cygwin

[Andrew Maximov]

> -----Original Message-----
> From: D.G.Somerton [mailto:dgsomerton at hunterwatertech.com.au]
> Sent: Monday, March 26, 2001 5:00 AM
> To: rtems
> Subject: cygwin
>
>
> Hello,
>
>   I have finally managed to get the RTems to compile on NT4 (sp6)
>
>   Firstly, I had to make a link in /bin to make cc an alias for gcc
>
>   Secondly, The configuration locked up and had to be killed.
>   The following change was required in ALL the configure scripts,
> except those in the tools subdirectory.
>
> #DGS:
>   ac_cv_prog_cc_works=yes>   ac_cv_prog_cc_cross=yes
> #if { (eval echo configure:1223: \"$ac_link\") 1>&5; (eval
> $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
> #  ac_cv_prog_cc_works=yes
> #  # If we can't run a trivial program, we are probably using a
> cross compiler.
> #  if (./conftest; exit) 2>/dev/null; then
> #    ac_cv_prog_cc_cross=no
> #  else
> #    ac_cv_prog_cc_cross=yes
> #  fi
> #else
> #  echo "configure: failed program was:" >&5
> #  cat conftest.$ac_ext >&5
> #  ac_cv_prog_cc_works=no
> #fi
>
>
> Something in this line
> #if { (eval echo configure:1223: \"$ac_link\") 1>&5; (eval
> $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
> was causing the lockup.
>
> I am using the pre-built binaries
> I am targeting the m68k
>
>
> D.G.Somerton
>
>
There is a more simple way. The problem is in the autoconf`s test. This test
is needed to detect: gcc is a cross-compiler or not ?
configure compile and try to run simply program. If execution of program
failed, then gcc is cross compiler.
But under WindowsNT or Windows2k if execution image has an unknown format
and if its size < 64K then this image is assumed as
16bit (.com) program and Windows tries to execute it. This is a reason of
lockup.The problem can be solved by 2 ways.
1. You can correct configure script.
2. Or you can prohibit execution of 16bits programs.
	( kill or rename ntvdm.exe in %SystemRoot%\system32 ) or
	hack registry: delete key
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW\cmdline"