Bug#515841: marked as done (gnat-4.3: fails to run Ada Conformity Assessment Test Suite)
Your message dated Mon, 02 Mar 2009 00:26:30 +0100
with message-id <87ljrox1sp.fsf@ludovic-brenta.org>
and subject line gnat-4.3: fails to run Ada Conformity Assessment Test Suite
has caused the Debian Bug report #515841,
regarding gnat-4.3: fails to run Ada Conformity Assessment Test Suite
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
515841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515841
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.3
Version: 4.3.2-1.1
Severity: minor
Justification: does not affect end users of the package
When building the package from source, the ACATS is enabled by default
but the logs in .../build/gcc/testsuite/ada/acats*/acats.log{.sep,}
show errors.
I have corrected part of these errors in 4.3.3-1 but there remains
this message:
<snipped>
splitting /home/lbrenta/src/debian/ram/gnat-4.3-4.3.3/build/gcc/testsuite/ada/acats0/support/impdefh.a into:
impdef-annex_h.ads
splitting /home/lbrenta/src/debian/ram/gnat-4.3-4.3.3/build/gcc/testsuite/ada/acats0/support/widechr.a into:
widechr.adb
**** Failed to compile macrosub
For the life of me I can't figure out why this error happens.
Compiling the file manually, whether with the system compiler or the
just-built compiler, works without a problem.
PS. The GNAT test suite works correctly though, and the log ends with:
=== gnat Summary ===
# of expected passes 401
# of expected failures 3
--
Ludovic Brenta.
--- End Message ---
--- Begin Message ---
Version: 4.3.3-2
The problem disappeared just as mysteriously as it appeared. I think
it was a code generation bug corrected by the update to the tip of
upstream's gcc-4_3-branch.
--
Ludovic Brenta.
--- End Message ---
Reply to: