Hi all,
Today I tried to get Blojsom to run inside Tomcat as distributed with FC4 test3 (with all updates applied as-of this morning). It bombed with an error in the log file about a malformed regular expression.
What is the correct place to report this bug?
Best regards,
Dave Orme
"David" == David J Orme david@db4o.com writes:
David> Today I tried to get Blojsom to run inside Tomcat as distributed with David> FC4 test3 (with all updates applied as-of this morning). It bombed with David> an error in the log file about a malformed regular expression.
David> What is the correct place to report this bug?
From the sound of it, either Classpath's bug tracker on savannah, or
gcc bugzilla (either is fine, sometime soon these should be merged).
However in general I think it is fine to report bugs to the Red Hat bugzilla. Sometimes they might be RH specific; and we can push them upstream after investigation. (This particular one is almost certainly an upstream bug.)
Tom
On Wed, 2005-05-25 at 14:32 -0500, David J. Orme wrote:
Today I tried to get Blojsom to run inside Tomcat as distributed with FC4 test3 (with all updates applied as-of this morning). It bombed with an error in the log file about a malformed regular expression.
You're probably seeing the same problem Anthony reported some time ago:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20435
I sent a classpath patch for review; the attached patch against blojsom should also do the trick. After applying it, blojsom seems to work fine -- at least for the obligatory screenshot :)
http://bootchart.org/misc/blojsom-gcj.png
Ziga Mahkovec wrote:
On Wed, 2005-05-25 at 14:32 -0500, David J. Orme wrote:
Today I tried to get Blojsom to run inside Tomcat as distributed with FC4 test3 (with all updates applied as-of this morning). It bombed with an error in the log file about a malformed regular expression.
You're probably seeing the same problem Anthony reported some time ago:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20435
I sent a classpath patch for review; the attached patch against blojsom should also do the trick. After applying it, blojsom seems to work fine -- at least for the obligatory screenshot :)
That's cool :D
java-devel@lists.fedoraproject.org