BZ #168: enableassertions/disableassertions command line handling wrong

Status fields:

This happens only with GNU classpath. Running "make check" in tests/regression/assertion
yields:

eatest1: FAILED
--- ./enabled.output    2008-09-18 10:46:45.000000000 +0200
+++ enabled.thisoutput  2012-03-13 16:15:53.000000000 +0100
@@ -1 +1 @@
-Assertions enabled!
+Assertions disabled!
eatest2: FAILED
--- ./enabled.output    2008-09-18 10:46:45.000000000 +0200
+++ enabled.thisoutput  2012-03-13 16:15:53.000000000 +0100
@@ -1 +1 @@
-Assertions enabled!
+Assertions disabled!
[...]
esatest1: FAILED
--- ./disabled.output   2008-09-18 10:46:45.000000000 +0200
+++ disabled.thisoutput 2012-03-13 16:15:57.000000000 +0100
@@ -1 +1 @@
-Assertions disabled!
+Assertions enabled!
esatest2: FAILED

The command line handling for these options seems slightly off.

Created an attachment (id=77)
enableassertion fix

This patch should fix the enableassertion issues with `make check'. The real problem is
in GNU Classpath as there is currently no way to distinguish between normal assertions
and system assertions. The topic has been discussed on the Classpath ML [1] and a patch
was proposed [2] but it has not yet found its way into the upstream repository.

Although, this patch was designed to work with the Classpath patch it fixes the `make
check' issue even if the Classpath issue is not fixed.

[1]: http://developer.classpath.org/pipermail/classpath/2012-April/003195.html
[2]: http://developer.classpath.org/pipermail/classpath-patches/2012-April/006690.html

In 1.6.0.