Follow-up Comment #67, bug #63808 (project groff): Hi Deri,
Regarding the %rom% issue, it looks likely to me that the "rom filesystem built into the executable" <https://ghostscript.com/docs/9.54.0/Use.htm> isn't really in the executable, but in the libgs9 dynamic shared object instead. At 20 MB it's way too big to attach on Savannah. $ size ~/tmp/gs-solaris10 ~/tmp/libgs.so.9.15-solaris10 text data bss dec hex filename 3025 236 328 3589 e05 /home/branden/tmp/gs-solaris10 4760075 14791376 3368 19554819 12a6203 /home/branden/tmp/libgs.so.9.15-solaris10 $ objdump -x ~/tmp/libgs.so.9.15-solaris10|grep -F .data|grep gs_romfs 00a0cb34 g O .data 00000004 gs_romfs_buildtime 00a16ad8 g O .data.rel.local 000003f8 gs_romfs $ objdump -x /usr/lib/x86_64-linux-gnu/libgs.so.9.53|grep -F .data|grep gs_romfs || echo NO MATCHES NO MATCHES $ size /usr/lib/x86_64-linux-gnu/libgs.so.9.53 text data bss dec hex filename 5936697 10509080 3808 16449585 fb0031 /usr/lib/x86_64-linux-gnu/libgs.so.9.53 So that's 14MB of data in the Solaris library, and 10MB in the Debian one. 4.3MB happens to be the size of the gs-fonts.tgz file you put up. Coincidence? Is there anything I can do to help you root out the data you're looking for? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63808> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
