Wanted the docs, so rebuilt libusb with the doc use flag set. The build failed when it reached the docs: ... libtool: link: i686-pc-linux-gnu-g++ -O2 -march=i686 -pipe -o .libs/driver_name driver_name.o -Wl,--as-needed ../.libs/libusbpp.so /var/tmp/portage/dev-libs/libusb-0.1.12-r5/work/libusb-0.1.12/.libs/libusb.so make[2]: Leaving directory `/var/tmp/portage/dev-libs/libusb-0.1.12-r5/work/libusb-0.1.12/tests' Making all in doc make[2]: Entering directory `/var/tmp/portage/dev-libs/libusb-0.1.12-r5/work/libusb-0.1.12/doc' rm -rf html mkdir html jade -t sgml -d ./website.dsl\#html ./manual.sgml jade:/etc/sgml/sgml-docbook-4.4.cat:1:8:E: cannot open "/usr/share/sgml/docbook/sgml-dtd-4.4/catalog" (No such file or directory) jade://etc/sgml/sgml-docbook-4.4.cat:1:8:E: cannot open "/usr/share/sgml/docbook/sgml-dtd-4.4/catalog" (No such file or directory) jade:/etc/sgml/sgml-docbook-4.4.cat:1:8:E: cannot open "/usr/share/sgml/docbook/sgml-dtd-4.4/catalog" (No such file or directory) ... Reproducible: Always Steps to Reproduce: 1. app-text/docbook-sgml-dtd-4.4 not present 2. dev-libs/libusb-1.0.8 present (without doc useflag) 3. Set the doc useflag in /etc/portage/package.use for dev-libs/libusb 4. emerge libusb Actual Results: ... libtool: link: i686-pc-linux-gnu-g++ -O2 -march=i686 -pipe -o .libs/driver_name driver_name.o -Wl,--as-needed ../.libs/libusbpp.so /var/tmp/portage/dev-libs/libusb-0.1.12-r5/work/libusb-0.1.12/.libs/libusb.so make[2]: Leaving directory `/var/tmp/portage/dev-libs/libusb-0.1.12-r5/work/libusb-0.1.12/tests' Making all in doc make[2]: Entering directory `/var/tmp/portage/dev-libs/libusb-0.1.12-r5/work/libusb-0.1.12/doc' rm -rf html mkdir html jade -t sgml -d ./website.dsl\#html ./manual.sgml jade:/etc/sgml/sgml-docbook-4.4.cat:1:8:E: cannot open "/usr/share/sgml/docbook/sgml-dtd-4.4/catalog" (No such file or directory) jade://etc/sgml/sgml-docbook-4.4.cat:1:8:E: cannot open "/usr/share/sgml/docbook/sgml-dtd-4.4/catalog" (No such file or directory) jade:/etc/sgml/sgml-docbook-4.4.cat:1:8:E: cannot open "/usr/share/sgml/docbook/sgml-dtd-4.4/catalog" (No such file or directory) ... Expected Results: This should have built libusb with the documents After manually emerging app-text/docbook-sgml-dtd (which brought in the 4.4 version), emerging libusb succeeded.
Created attachment 257415 [details] emerge --info
Hi, Please attach /var/tmp/portage/dev-libs/libusb-1.0.8/temp/build.log Thanks!
Created attachment 257416 [details] Build log
(In reply to comment #3) > Created an attachment (id=257416) [details] > Build log > Sorry, I got the wrong version number in the main part of the bug report. Didn't notice that I had two versions of libusb installed.
No worries. Fixed the summary to reflect the problem version. Assigning to maintainer.
problem with the jade/docbook install. libusb itself doesn't need 4.4.
this is in fact a jade bug jade -t sgml -d ./website.dsl\#html ./manual.sgml jade:./manual.sgml:1:55:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook V4.2//EN" jade:./manual.sgml:10:0:E: reference to entity "BOOK" for which no system identifier could be generated jade:./manual.sgml:1:0: entity was defined here jade:./manual.sgml:10:0:E: DTD did not contain element declaration for document type name jade:./manual.sgml:12:9:E: there is no attribute "ID" -------------------------------------------------- archtester ~ # jade -t sgml -d ./website.dsl\#html ./manual.sgml jade:E: cannot find "./manual.sgml"; tried "./manual.sgml", "/usr/share/sgml/./manual.sgml" jade:E: cannot find "./website.dsl"; tried "./website.dsl", "/usr/share/sgml/./website.dsl" jade:E: specification document does not have the DSSSL architecture as a base architecture jade:E: no style-specification or external-specification with ID "html" jad is poking around looking for files like manual.sgml which are not to be found.
Has this been fixed in dev-libs/libusb-0.1.12-r7 which DEPENDs on doc? ( .. ~app-text/docbook-sgml-dtd-4.2 ) ?
That's strange: this problem is fixed on ~amd64, but is present on ~x86 undergoing a deep update now. After update will be finished I'll try to reemerge again.
Now libusb:0 build fine on both ~x86 and ~amd64.
