When compiling a .jar, gcj will compile all the resources in
the .jar into the resulting .o. when using the .db feature,
resources in the .so will never be used; instead they'll always
be pulled from the original .jar. gcj could use an option to
omit resources from the compilation, to avoid unnecessarily
bloating the .o.