tried to emerge gpdf 2.8.1 since 2.8.0-r2 did not compile either and glsa requires that I update. /bin/install: cannot stat `gpdf-C.omf.out': No such file or directory make[4]: *** [install-data-hook-omf] Error 1 make[4]: Leaving directory `/usr/portage/tmp/portage/gpdf-2.8.1/work/gpdf-2.8.1/help/C' Reproducible: Always Steps to Reproduce: 1.unmask 2.8.1 2.emerge gpdf 3. Actual Results: mkdir -p -- /usr/portage/new/../tmp/portage/gpdf-2.8.1/image//usr/share/gnome/ help/gpdf/C/figures make install-data-hook make[4]: Entering directory `/usr/portage/tmp/portage/gpdf-2.8.1/work/gpdf-2.8. 1/help/C' /bin/sh ../../mkinstalldirs /usr/portage/new/../tmp/portage/gpdf-2.8.1/image// usr/share/omf/gpdf mkdir -p -- /usr/portage/new/../tmp/portage/gpdf-2.8.1/image//usr/share/omf/gpdf for file in gpdf-C.omf; do \ /bin/install -c -m 644 $file.out /usr/portage/new/../tmp/portage/gpdf-2. 8.1/image//usr/share/omf/gpdf/$file; \ done /bin/install: cannot stat `gpdf-C.omf.out': No such file or directory make[4]: *** [install-data-hook-omf] Error 1 make[4]: Leaving directory `/usr/portage/tmp/portage/gpdf-2.8.1/work/gpdf-2.8.1/ help/C' Expected Results: a clean compile. Got what looks like the same error off 2.8.0-r2 make[4]: Entering directory `/usr/portage/tmp/portage/gpdf-2.8.0-r2/work/gpdf-2. 8.0/help/C' /bin/sh ../../mkinstalldirs /usr/portage/new/../tmp/portage/gpdf-2.8.0-r2/image/ /usr/share/omf/gpdf mkdir -p -- /usr/portage/new/../tmp/portage/gpdf-2.8.0-r2/image//usr/share/omf/ gpdf for file in gpdf-C.omf; do \ /bin/install -c -m 644 $file.out /usr/portage/new/../tmp/portage/gpdf-2. 8.0-r2/image//usr/share/omf/gpdf/$file; \ done /bin/install: cannot stat `gpdf-C.omf.out': No such file or directory make[4]: *** [install-data-hook-omf] Error 1 make[4]: Leaving directory `/usr/portage/tmp/portage/gpdf-2.8.0-r2/work/gpdf-2. 8.0/help/C' ERROR: app-text/gpdf-2.8.0-r2 failed.
Sounds like a docbook related error, make sure you have the newest app-text/docbook-* packages. If updating them doesnt help, please try running build-docbook-catalog (as root). Finally, _attach_ a _full_ log to this report and we'll try and work it out. Thanks.
Also, what version of scrollkeeper are you running?
needinfo
Thanks for the suggestion Mike. I cleared the problem by unmerging docbook entirely and rebuilding it. It was the current lastest version so the same version was emerged back in. This action was sufficient to clear the problem. Thanks for pointing me in the right direction. Regards.