You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Tim Landscheidt <ti...@tim-landscheidt.de> on 2003/04/18 15:31:43 UTC
Running FOP with gij
Hi,
I'm trying to get FOP to run with gij (basically because
that is Red Hat's JDK of choice). A small test reveals:
| [tim@lockfix ~/src/fop-0.20.5rc2]$ CLASSPATH=build/fop.jar:lib/xml-apis.jar:lib/avalon-framework-cvs-20020806.jar:lib/batik.jar:lib/xalan-2.4.1.jar:lib/xercesImpl-2.2.1.jar gij org.apache.fop.apps.Fop -xml ../julis/julibrief-fo/beko2002-1.xml -xsl ../julis/julibrief-fo/julibrief-fo.xsl -pdf /var/tmp/test.pdf
| [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
| Exception in thread "main" java.lang.VerifyError: verification failed at PC 122 in org.apache.xalan.transformer.TransformerImpl:createResultContentHandler((Ljavax.xml.transform.Result;Lorg.apache.xalan.templates.OutputProperties;)Lorg.xml.sax.ContentHandler;): incompatible type on stack
| at 0x4027615f: java.lang.Throwable.Throwable(java.lang.String) (/usr/lib/libgcj.so.3)
| at 0x4026908e: java.lang.Error.Error(java.lang.String) (/usr/lib/libgcj.so.3)
| at 0x4026ab1a: java.lang.LinkageError.LinkageError(java.lang.String) (/usr/lib/libgcj.so.3)
| at 0x402764fe: java.lang.VerifyError.VerifyError(java.lang.String) (/usr/lib/libgcj.so.3)
| at 0x4024cac9: _Jv_BytecodeVerifier.verify_fail(byte, int) (/usr/lib/libgcj.so.3)
| at 0x4023fc4d: _Jv_BytecodeVerifier.verify_instructions_0() (/usr/lib/libgcj.so.3)
| at 0x4023e697: _Jv_VerifyMethod(_Jv_InterpMethod) (/usr/lib/libgcj.so.3)
| at 0x40236a24: _Jv_PrepareClass(java.lang.Class) (/usr/lib/libgcj.so.3)
| at 0x40255568: java.lang.ClassLoader.linkClass0(java.lang.Class) (/usr/lib/libgcj.so.3)
| at 0x40268073: java.lang.ClassLoader.resolveClass0(java.lang.Class) (/usr/lib/libgcj.so.3)
| at 0x4025399c: java.lang.Class.initializeClass() (/usr/lib/libgcj.so.3)
| at 0x4023d74b: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40392347: ffi_call_SYSV (/usr/lib/libgcj.so.3)
| at 0x40392307: ffi_raw_call (/usr/lib/libgcj.so.3)
| at 0x4023d528: _Jv_InterpMethod.continue1(_Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023de34: _Jv_InterpMethod.run(ffi_cif, void, ffi_raw, _Jv_InterpMethodInvocation) (/usr/lib/libgcj.so.3)
| at 0x4023b424: _Jv_InterpMethod.run_normal(ffi_cif, void, ffi_raw, void) (/usr/lib/libgcj.so.3)
| at 0x403921bc: ?? (??:0)
| at 0x40250308: gnu.gcj.runtime.FirstThread.call_main() (/usr/lib/libgcj.so.3)
| at 0x402bb0b1: gnu.gcj.runtime.FirstThread.run() (/usr/lib/libgcj.so.3)
| at 0x4025cfdc: _Jv_ThreadRun(java.lang.Thread) (/usr/lib/libgcj.so.3)
| at 0x4022978c: _Jv_RunMain(java.lang.Class, byte const, int, byte const, boolean) (/usr/lib/libgcj.so.3)
| at 0x08048900: ?? (??:0)
| at 0x4068b907: __libc_start_main (/lib/libc.so.6)
| at 0x080486c1: ?? (??:0)
Though I understand that this is not a FOP question per se,
maybe someone has already travelled along this path :-).
Does anyone know what this verification error in Xalan
means? I tested this also with Xalan-J 2.5.0 (and the in-
cluded Xerces-J 2.4.0) and the only difference is that the
error then occurs at "PC 120".
TIA,
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Running FOP with gij
Posted by Tim Landscheidt <ti...@tim-landscheidt.de>.
Jeremias Maerki <de...@greenmail.ch> wrote:
> I don't think there's a patch around for that. If you think making AWT
> optional is important please file a "request for enhancement" in
> BugZilla for future reference so we can respect that in the redesign.
Half a year (minus some hours) ago, I filed bug #14679 :-).
> I think it should be relatively simple to make AWT optional. Basically
> two steps are necessary:
> - Modify build.xml so only the AWT-dependant classes can be compiled
> conditionally.
> - Modify the classes that have AWT-dependant stuff in them so they run
> without AWT (see Jimi, JAI and JCE support as an example).
> There are special AWT-backends out there for headless servers. Maybe
> there's also a dummy AWT package somewhere. Just a thought.
I will look into this. Thanks!
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Running FOP with gij
Posted by Jeremias Maerki <de...@greenmail.ch>.
I don't think there's a patch around for that. If you think making AWT
optional is important please file a "request for enhancement" in
BugZilla for future reference so we can respect that in the redesign.
I think it should be relatively simple to make AWT optional. Basically
two steps are necessary:
- Modify build.xml so only the AWT-dependant classes can be compiled
conditionally.
- Modify the classes that have AWT-dependant stuff in them so they run
without AWT (see Jimi, JAI and JCE support as an example).
There are special AWT-backends out there for headless servers. Maybe
there's also a dummy AWT package somewhere. Just a thought.
On 18.04.2003 16:26:22 Tim Landscheidt wrote:
> okay, some googling showed that the culprit is gij :-(.
>
> Another question in this regard: Has anybody played with
> FOP and gcj? Some time ago, the AWT viewer was a problem as
> gcj did not provide any Swing classes. Is there any patch
> available that deletes all references to the AWT viewer?
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Running FOP with gij
Posted by Tim Landscheidt <ti...@tim-landscheidt.de>.
Hi,
okay, some googling showed that the culprit is gij :-(.
Another question in this regard: Has anybody played with
FOP and gcj? Some time ago, the AWT viewer was a problem as
gcj did not provide any Swing classes. Is there any patch
available that deletes all references to the AWT viewer?
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org