Since compiling groff fails with uclibc, it might be a good thing to remove the groff dependency... It would have no effect on building Xorg. (tested xorg-x11-6.8.2-r6) Reproducible: Always Steps to Reproduce: 1. remove groff dependency 2. ebuild xorg-x11[version].ebuild digest 3. emerge xorg-x11 Actual Results: X installed without groff # IN PATCH-FORM --- xorg-x11-6.8.2-r6.ebuild 2005-10-03 21:50:38.000000000 +0200 +++ xorg-x11-6.8.2-r7.ebuild 2005-10-10 14:39:53.000000000 +0200 @@ -80,7 +80,7 @@ DEPEND=">=sys-libs/ncurses-5.1 >=sys-libs/zlib-1.1.3-r2 >=sys-devel/flex-2.5.4a-r5 - sys-apps/groff + !uclibc? (sys-apps/groff) >=dev-libs/expat-1.95.3 >=media-libs/freetype-2.1.8 >=media-libs/fontconfig-2.1-r1
*** This bug has been marked as a duplicate of 98187 ***
Ok, this is about/for Xorg, not groff. It does have a relation to groff, but thats where it end's imho.
your comment: Since compiling groff fails with uclibc is unrelated to xorg
(In reply to comment #3) > your comment: > Since compiling groff fails with uclibc > is unrelated to xorg Correct. This is both a way around groff AND a way to minimize the size of Xorg. For fome parts it could be that groff is needed since there where reports of Xorg failing on groff's absence. "emerge -e system fail" - kind of reports.