If you use the new java configuration toolkit there's no user CLASSPATH any more (it is deprecated). If you want to use fop with jai and/or jimi support it complains about missing classes. The reason for this seems to be the setting of the CLASSPATH in the fop start script (/usr/bin/fop): cp=${CLASSPATH}:`java-config -p avalon-framework-4.1,batik-1.5,fop,xalan,xerces-2` Depending on the USE flags "sun-jai-bin" or "sun-jimi" should be added there. ---------- This is how i compiled fop: [ebuild R ] dev-java/fop-0.20.5-r3 USE="jai jimi -doc -examples"
Should be fixed with fop-0.20.5-r5. Thanks for reporting! Give it a few hours to hit your local rsync, then do an emerge --sync.