[Bug ada/21611] New: ACATS Failures After Successfully Built using Cygwin 3.3.3

[Bug ada/21611] New: ACATS Failures After Successfully Built using Cygwin 3.3.3

[anh_vn_vo at yahoo dot com]

Successfully built Ada compiler. When performing acats test, the test summary 
shown below indicates the failures.

make: Entering directory `/cygdrive/d/Build-Ada/gcc'
test -d testsuite/ada/acats || mkdir -p testsuite/ada/acats
testdir=`cd ../../gcc-4.0-20050430/gcc/testsuite/ada/acats; ${PWDCMD-pwd}`; \
export testdir; cd testsuite/ada/acats; ${testdir}/run_acats 
		=== acats configuration ===
target gcc is /cygdrive/d/Build-Ada/gcc/xgcc -B/cygdrive/d/Build-Ada/gcc/
Reading specs from /cygdrive/d/Build-Ada/gcc/specs Target: i686-pc-cygwin 
Configured with: ../gcc-4.0-20050430/configure --enable-languages=ada --enable-
threads=gnat Thread model: gnat gcc version 4.0.1 20050430 (prerelease)
host=i686-pc-cygwin
target=i686-pc-cygwin
gnatmake is /cygdrive/d/Build-Ada/gcc/gnatmake

		=== acats support ===
Generating support files... done.
Compiling support files... done.

		=== acats tests ===
Running chapter a ...
Running chapter c2 ...
FAIL:	c23003b
FAIL:	c23003g
FAIL:	c23003i
Running chapter c3 ...
Running chapter c4 ...
Running chapter c5 ...
Running chapter c6 ...
FAIL:	c62003a
FAIL:	c62003b
FAIL:	c64103e
FAIL:	c64103f
FAIL:	c64104h
FAIL:	c64104j
FAIL:	c64104k
FAIL:	c64104l
FAIL:	c64104n
Running chapter c7 ...
Running chapter c8 ...
Running chapter c9 ...
FAIL:	c96005d
Running chapter ca ...
Running chapter cb ...
FAIL:	cb3004a
FAIL:	cb4001a
Running chapter cc ...
FAIL:	cc3017c
/cygdrive/d/gcc-4.0-20050430/gcc/testsuite/ada/acats/run_all.sh: cannot 
create /cygdrive/d/Build-Ada/gcc/testsuite/ada/acats/acats.log: error 16
make: *** [check-gnat] Error 2
make: Leaving directory `/cygdrive/d/Build-Ada/gcc'

-- 
           Summary: ACATS Failures After Successfully Built using Cygwin
                    3.3.3
           Product: gcc
           Version: 4.0.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: anh_vn_vo at yahoo dot com
                CC: gcc-bugs at gcc dot gnu dot org
  GCC host triplet: PC Running Cygwin under XP


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21611

[Bug ada/21611] ACATS Failures After Successfully Built using Cygwin 3.3.3

[anh_vn_vo at yahoo dot com]

------- Additional Comments From anh_vn_vo at yahoo dot com  2005-05-18 01:06 -------
After further checking, the run-time support was not built. In fact, running 
any Ada code containing Ada task triggers "failed run-time assertion : Tasking 
not implemented on this configuration" error message. This problem occurs even 
though option --enable-threads=gnat was set in the configuration. Looking 
around the source code, a possible bug at line 1277 of Makefile.in under 
subdirectory ../gcc/ada. The word cygwin32 should be changed to cygwin because 
only the name cygwin, in i686-pc-cygwin, was generated in the Makefile 
resulting from executing configure command.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21611

[Bug ada/21611] ACATS Failures After Successfully Built using Cygwin 3.3.3

[charlet at gcc dot gnu dot org]

------- Additional Comments From charlet at gcc dot gnu dot org  2005-05-18 08:12 -------
The last error seems to be related to the cygwin environment.
There is also no point in reporting such results as a bug, since there are
separate issues, which all seem to be related to cygwin rather than gcc.

Arno

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21611

[Bug ada/21611] ACATS Failures After Successfully Built using Cygwin 3.3.3

[anh_vn_vo at yahoo dot com]

------- Additional Comments From anh_vn_vo at yahoo dot com  2005-05-18 15:35 -------
If it is expected that the name cygwin32 instead just cygwin generated during 
configuration step, I agree that it is cygwin environment issue. Therefore, I 
would like to withdraw my report. Otherwise, further investigation is needed to 
make sure which part this problem belongs to, cygwin or gcc.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21611