Re: [blfs-dev] Why do we patch polkit for elogind ?
On Tue, Jan 05, 2021 at 10:20:51PM +, Ken Moffat via blfs-dev wrote: > On Tue, Jan 05, 2021 at 07:50:14PM +, Ken Moffat via blfs-dev wrote: > > On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote: > > > On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote: > > > > On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev > > > > wrote: > > > > > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > > > > > > Just checking all packages, the following are present: > > > > > Replying with the state of play before Pierre had identified that > using -i is what can cause gtkdocize to be required (i.e. for > packages which mention gtk-doc if I understood correctly) : > > > > networking/netprogs/cifsutils.xml: autoreconf -fiv > I guess my mail to Doug got treated as spam, as will this one. > There seems to be a perfectly usable configure script in all > versions of cifs-utils that have been in the book since this > autoreconf was added - I have not tried to run autoreconf on this. > > > > > > > networking/netlibs/libnsl.xml: autoreconf -fi > > > > Not yet tested. gtkdocize not required. > > > > x/lib/clutter.xml: autoreconf -f -i > This has been commented out. > > > > x/lib/cairo.xml: autoreconf -fiv > gtkdocize is needed, I can test without -i. Is ok without the -i, but even if gtk-doc is installed it defaults to no docs: checking whether to build gtk-doc documentation... no In this case, --enable-gtk-doc is needed to *build* the docs if gtk-doc has been installed, unlike e.g. libgrss where the switch controls *rebuilding* the docs. > > > > postlfs/filesystems/reiser.xml:autoreconf -fiv > gtkdocize not required. > > > > postlfs/security/volume_key.xml: autoreconf -fiv > gtkdocize not required. > > > > > > > postlfs/security/polkit.xml: autoreconf -fi > gtkdocize is needed for this, but up-thread Pierre said we don't > need -i. > > > > postlfs/security/tripwire.xml: autoreconf -fi > gtkdocize not required. > > > > multimedia/libdriv/libmad.xml: autoreconf -fi > I seem to have missed this one. Ah, no, it's another one that has > been commented out. > > > > general/graphlib/sassc.xml:autoreconf -fi > gtkdocize not needed. For testing with DESTDIR pass --with-libsass= > to point to where the lib was installed. > > > > general/graphlib/libraw.xml: autoreconf -fiv > gtkdocize not required. > > > > general/genlib/telepathy-glib.xml: autoreconf -fiv > Needs gtkdocize, I think I have the deps to test without -i. > Fails badly, it needs -fi AND gtk-doc for autoreconf. After that, one of the tests is still using /usr/bin/python which I do not have normally available: = Telepathy-GLib 0.24.1: tests/test-suite.log = # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: all-errors-documented.py == ../build-aux/test-driver: ./all-errors-documented.py: /usr/bin/python: bad interpreter: No such file or directory FAIL all-errors-documented.py (exit status: 126) Looking for /usr/bin/python finds: terpreter: No such file or directory ./tests/all-errors-documented.py.log:../build-aux/test-driver: ./all-errors-documented.py: /usr/bin/python: bad interpreter: No such file or directory ./tests/Makefile:PYTHON = /usr/bin/python3 ./tests/all-errors-documented.py:#!/usr/bin/python <<< ./tests/tools/Makefile:PYTHON = /usr/bin/python3 ./tests/lib/Makefile:PYTHON = /usr/bin/python3 ./tests/dbus/Makefile:PYTHON = /usr/bin/python3 Adding sed -i 's%/usr/bin/python%&3%' tests/all-errors-documented.py fixes that and allows the second set of tests to run. > > > general/genlib/libunique.xml: autoreconf -fi > Needs gtkdocize, I think I have the deps to test without -i. > This too needs the -i in autoreconf. > > > general/genlib/libgrss.xml:autoreconf -fiv > Needs gtkdocize, I think I have the deps to test without -i. > Without the -i, libgrss builds fine. > > > general/genlib/exempi.xml: autoreconf -fiv > gtkdocize is not required. > > > > general/genlib/libpaper.xml: autoreconf -fi > gtkdocize is not required. > > > > > > > general/genutils/gtk-doc.xml: autoreconf -fiv > gtkdocize is not required. > > > > pst/sgml/sgml-common.xml: autoreconf -f -i > gtkdocize is not required. > > > > xsoft/other/tigervnc.xml: autoreconf -fiv > gtkdocize is not required. > > > Now I just need to edit all of these, and comment the autoreconf in cogl (from last week). ĸen -- Lu-Tze had long considered that everything happens for a reason, except possibly football. -- The Thief Of Time -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On Tue, Jan 05, 2021 at 05:29:53PM -0600, Douglas R. Reno via blfs-dev wrote: > > On 1/5/21 4:20 PM, Ken Moffat via blfs-dev wrote: > > On Tue, Jan 05, 2021 at 07:50:14PM +, Ken Moffat via blfs-dev wrote: > > > On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote: > > > > On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote: > > > > > On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via > > > > > blfs-dev wrote: > > > > > > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > > > > Just checking all packages, the following are present: > > > > > > Replying with the state of play before Pierre had identified that > > using -i is what can cause gtkdocize to be required (i.e. for > > packages which mention gtk-doc if I understood correctly) : > > > > > > networking/netprogs/cifsutils.xml: autoreconf -fiv > > I guess my mail to Doug got treated as spam, as will this one. > > There seems to be a perfectly usable configure script in all > > versions of cifs-utils that have been in the book since this > > autoreconf was added - I have not tried to run autoreconf on this. > > Unfortunately I can't find it in my spam folder over in GMail either :-( > > Yeah the autoreconf command can go from cifs-utils. There was a broken > release of (6.9?), which later had a stealth release that restored the > proper behavior. 6.9 (Broken) didn't ship with a pregenerated configure > file. > > I'll get it at my next commit, unless you get to it first :-) > > - Doug > Thanks for the explanation, keeping track of where there was a stealth update which we fixed seems quite hard. I'm not likely to commit any of this soon. ĸen -- Lu-Tze had long considered that everything happens for a reason, except possibly football. -- The Thief Of Time -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On 1/5/21 4:20 PM, Ken Moffat via blfs-dev wrote: On Tue, Jan 05, 2021 at 07:50:14PM +, Ken Moffat via blfs-dev wrote: On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote: On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote: On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev wrote: On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: Just checking all packages, the following are present: Replying with the state of play before Pierre had identified that using -i is what can cause gtkdocize to be required (i.e. for packages which mention gtk-doc if I understood correctly) : networking/netprogs/cifsutils.xml: autoreconf -fiv I guess my mail to Doug got treated as spam, as will this one. There seems to be a perfectly usable configure script in all versions of cifs-utils that have been in the book since this autoreconf was added - I have not tried to run autoreconf on this. Unfortunately I can't find it in my spam folder over in GMail either :-( Yeah the autoreconf command can go from cifs-utils. There was a broken release of (6.9?), which later had a stealth release that restored the proper behavior. 6.9 (Broken) didn't ship with a pregenerated configure file. I'll get it at my next commit, unless you get to it first :-) - Doug -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On Tue, Jan 05, 2021 at 07:50:14PM +, Ken Moffat via blfs-dev wrote: > On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote: > > On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote: > > > On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev > > > wrote: > > > > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > > > > Just checking all packages, the following are present: > > Replying with the state of play before Pierre had identified that using -i is what can cause gtkdocize to be required (i.e. for packages which mention gtk-doc if I understood correctly) : > > networking/netprogs/cifsutils.xml: autoreconf -fiv I guess my mail to Doug got treated as spam, as will this one. There seems to be a perfectly usable configure script in all versions of cifs-utils that have been in the book since this autoreconf was added - I have not tried to run autoreconf on this. > > > > networking/netlibs/libnsl.xml: autoreconf -fi > > Not yet tested. > > x/lib/clutter.xml: autoreconf -f -i This has been commented out. > > x/lib/cairo.xml: autoreconf -fiv gtkdocize is needed, I can test without -i. > > postlfs/filesystems/reiser.xml:autoreconf -fiv gtkdocize not required. > > postlfs/security/volume_key.xml: autoreconf -fiv gtkdocize not required. > > > > postlfs/security/polkit.xml: autoreconf -fi gtkdocize is needed for this, but up-thread Pierre said we don't need -i. > > postlfs/security/tripwire.xml: autoreconf -fi gtkdocize not required. > > multimedia/libdriv/libmad.xml: autoreconf -fi I seem to have missed this one. Ah, no, it's another one that has been commented out. > > general/graphlib/sassc.xml:autoreconf -fi gtkdocize not needed. For testing with DESTDIR pass --with-libsass= to point to where the lib was installed. > > general/graphlib/libraw.xml: autoreconf -fiv gtkdocize not required. > > general/genlib/telepathy-glib.xml: autoreconf -fiv Needs gtkdocize, I think I have the deps to test without -i. > > general/genlib/libunique.xml: autoreconf -fi Needs gtkdocize, I think I have the deps to test without -i. > > general/genlib/libgrss.xml:autoreconf -fiv Needs gtkdocize, I think I have the deps to test without -i. > > general/genlib/exempi.xml: autoreconf -fiv gtkdocize is not required. > > general/genlib/libpaper.xml: autoreconf -fi gtkdocize is not required. > > > > general/genutils/gtk-doc.xml: autoreconf -fiv gtkdocize is not required. > > pst/sgml/sgml-common.xml: autoreconf -f -i gtkdocize is not required. > > xsoft/other/tigervnc.xml: autoreconf -fiv gtkdocize is not required. > > > > I didn't check the individual pages, but perhaps they all should use -fv. > > We would need to do a test build at least though make to ensure the > > instructions still work. > > > > -- Bruce > > That's what I meant (for "do the current instructions need > gtkdocize" I've already completed), and for some of those (few) that > do, I have the deps and can see if dropping -i solves things. > So, it looks like I still have one to test, one non-book package to test, and a few to retest without -i. ĸen -- Lu-Tze had long considered that everything happens for a reason, except possibly football. -- The Thief Of Time -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Error building libxslt-1.1.34
On 1/5/21 11:34 AM, Pierre Labastie via blfs-dev wrote: On Tue, 2021-01-05 at 09:58 +0100, Tim Tassonis via blfs-dev wrote: Hi all I am stuck at building libxslt-1.1.34, getting the following error: I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd doc/xsltproc.xml:8: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; ]> For the record, the URL "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; works fine with curl or the browser. While I first ignored this error, it now really bites mime at shared-mime-info. I have installed both docbook-xml-4.5 and docbook-xsl-1.79.2, and also libxml2, but not any other docbook stuff. Does anybody know where this error is coming from? Guessing: you haven't run the instructions in the "Configuration" paragraph of docbook-xml-4.5. And so it was. I forgot the for DTDVERSION in 4.1.2 4.2 4.3 4.4 do ... loop. Now, all is wekll. Sorry for the noise. Bye Tim -- decentral.ch - IT Stuff Tim Tassonis Hohlstrasse 400 c/o Baubüro Insitu 8048 Zürich st...@decentral.ch +41 79 229 36 17 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote: > On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote: > > On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev > > wrote: > > > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > > > > Hi Guys, > > > > > > > > some of you may have noticed that I have an aversion to gtk-doc (I'm > > > > getting over it). This was triggered by occasional uses of > > > > autoreconf now needing gtkdocize. That first hit me in polkit with > > > > the patch for elogind, but my memory suggested that the patch has in > > > > the past been added or rolled forward a little after updates to > > > > polkit. > > > > > > > > > > From reading the patch that introduced gtkdocize in autoconf [1], > > > it appears that gtkdocize is not called if the -i (--install) flags is > > > not passed. That flag is not needed for polkit. We might want to check > > > whether it is really needed for the other packages that use autoreconf. > > > > > > Pierre > > > > > > > Interesting, but I'm not sure I can check that throughout - I've > > checked plain "does autoreconf work to produce a configure script" > > on several packages where I lack the dependencies to actually build > > them. > > Just checking all packages, the following are present: > > networking/netprogs/cifsutils.xml: autoreconf -fiv > > networking/netlibs/libnsl.xml: autoreconf -fi > > x/lib/clutter.xml: autoreconf -f -i > x/lib/cairo.xml: autoreconf -fiv > postlfs/filesystems/reiser.xml:autoreconf -fiv > postlfs/security/volume_key.xml: autoreconf -fiv > > postlfs/security/polkit.xml: autoreconf -fi > postlfs/security/tripwire.xml: autoreconf -fi > multimedia/libdriv/libmad.xml: autoreconf -fi > general/graphlib/sassc.xml:autoreconf -fi > general/graphlib/libraw.xml: autoreconf -fiv > general/genlib/telepathy-glib.xml: autoreconf -fiv > general/genlib/libunique.xml: autoreconf -fi > general/genlib/libgrss.xml:autoreconf -fiv > general/genlib/exempi.xml: autoreconf -fiv > general/genlib/libpaper.xml: autoreconf -fi > > general/genutils/gtk-doc.xml: autoreconf -fiv > pst/sgml/sgml-common.xml: autoreconf -f -i > xsoft/other/tigervnc.xml: autoreconf -fiv > > I didn't check the individual pages, but perhaps they all should use -fv. > We would need to do a test build at least though make to ensure the > instructions still work. > > -- Bruce That's what I meant (for "do the current instructions need gtkdocize" I've already completed), and for some of those (few) that do, I have the deps and can see if dropping -i solves things. The list of those where gtkdocize is needed but I might not have the deps for a full build is on another machine, will report back later. ĸen -- Lu-Tze had long considered that everything happens for a reason, except possibly football. -- The Thief Of Time -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote: On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev wrote: On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: Hi Guys, some of you may have noticed that I have an aversion to gtk-doc (I'm getting over it). This was triggered by occasional uses of autoreconf now needing gtkdocize. That first hit me in polkit with the patch for elogind, but my memory suggested that the patch has in the past been added or rolled forward a little after updates to polkit. From reading the patch that introduced gtkdocize in autoconf [1], it appears that gtkdocize is not called if the -i (--install) flags is not passed. That flag is not needed for polkit. We might want to check whether it is really needed for the other packages that use autoreconf. Pierre Interesting, but I'm not sure I can check that throughout - I've checked plain "does autoreconf work to produce a configure script" on several packages where I lack the dependencies to actually build them. Just checking all packages, the following are present: networking/netprogs/cifsutils.xml: autoreconf -fiv networking/netlibs/libnsl.xml: autoreconf -fi x/lib/clutter.xml: autoreconf -f -i x/lib/cairo.xml: autoreconf -fiv postlfs/filesystems/reiser.xml:autoreconf -fiv postlfs/security/volume_key.xml: autoreconf -fiv postlfs/security/polkit.xml: autoreconf -fi postlfs/security/tripwire.xml: autoreconf -fi multimedia/libdriv/libmad.xml: autoreconf -fi general/graphlib/sassc.xml:autoreconf -fi general/graphlib/libraw.xml: autoreconf -fiv general/genlib/telepathy-glib.xml: autoreconf -fiv general/genlib/libunique.xml: autoreconf -fi general/genlib/libgrss.xml:autoreconf -fiv general/genlib/exempi.xml: autoreconf -fiv general/genlib/libpaper.xml: autoreconf -fi general/genutils/gtk-doc.xml: autoreconf -fiv pst/sgml/sgml-common.xml: autoreconf -f -i xsoft/other/tigervnc.xml: autoreconf -fiv I didn't check the individual pages, but perhaps they all should use -fv. We would need to do a test build at least though make to ensure the instructions still work. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On Tue, 2021-01-05 at 14:33 +0100, Pierre Labastie via blfs-dev wrote: > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > > Hi Guys, > > > > some of you may have noticed that I have an aversion to gtk-doc > > (I'm > > getting over it). This was triggered by occasional uses of > > autoreconf now needing gtkdocize. That first hit me in polkit with > > the patch for elogind, but my memory suggested that the patch has > > in > > the past been added or rolled forward a little after updates to > > polkit. > > > > From reading the patch that introduced gtkdocize in autoconf [1], > it appears that gtkdocize is not called if the -i (--install) flags > is > not passed. That flag is not needed for polkit. We might want to > check > whether it is really needed for the other packages that use > autoreconf. Forgot the ref... [1] http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=blobdiff;f=bin/autoreconf.in;h=14e12895e2a2d98729dc19f38e442626f1d72444;hp=1ca11f284a0ba02cc92e4b96ce13be2b69769691;hb=dd880a0a6de5602cdd40b770ed6b083b34aa0768;hpb=aba75f6d4a9c875a9d5d90a07c6b3678db66a4bf -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev wrote: > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > > Hi Guys, > > > > some of you may have noticed that I have an aversion to gtk-doc (I'm > > getting over it). This was triggered by occasional uses of > > autoreconf now needing gtkdocize. That first hit me in polkit with > > the patch for elogind, but my memory suggested that the patch has in > > the past been added or rolled forward a little after updates to > > polkit. > > > > From reading the patch that introduced gtkdocize in autoconf [1], > it appears that gtkdocize is not called if the -i (--install) flags is > not passed. That flag is not needed for polkit. We might want to check > whether it is really needed for the other packages that use autoreconf. > > Pierre > Interesting, but I'm not sure I can check that throughout - I've checked plain "does autoreconf work to produce a configure script" on several packages where I lack the dependencies to actually build them. ĸen -- Lu-Tze had long considered that everything happens for a reason, except possibly football. -- The Thief Of Time -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Additional Qt 6 finding
Some of the modules that used to be in the main /qt/ directory are now found in https://download.qt-project.org/official_releases/additional_libraries/ I see that the most recent poppler has a qt6 in addition to the qt5 library, which Arch is building, but nothing is using it yet. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Why do we patch polkit for elogind ?
On Wed, 2020-12-30 at 18:21 +, Ken Moffat via blfs-dev wrote: > Hi Guys, > > some of you may have noticed that I have an aversion to gtk-doc (I'm > getting over it). This was triggered by occasional uses of > autoreconf now needing gtkdocize. That first hit me in polkit with > the patch for elogind, but my memory suggested that the patch has in > the past been added or rolled forward a little after updates to > polkit. > From reading the patch that introduced gtkdocize in autoconf [1], it appears that gtkdocize is not called if the -i (--install) flags is not passed. That flag is not needed for polkit. We might want to check whether it is really needed for the other packages that use autoreconf. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Error building libxslt-1.1.34
On Tue, 2021-01-05 at 09:58 +0100, Tim Tassonis via blfs-dev wrote: > Hi all > > I am stuck at building libxslt-1.1.34, getting the following error: > > > > I/O error : Attempt to load network entity > http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd > doc/xsltproc.xml:8: warning: failed to load external entity > "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; > ]> > > > > For the record, the URL > "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; works fine > with curl or the browser. While I first ignored this error, it now > really bites mime at shared-mime-info. > > I have installed both docbook-xml-4.5 and docbook-xsl-1.79.2, and > also > libxml2, but not any other docbook stuff. > > Does anybody know where this error is coming from? > Guessing: you haven't run the instructions in the "Configuration" paragraph of docbook-xml-4.5. Note: usually, xsltproc is run with the --nonet switch, so that loading an external entity fails if it is not present locally. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Error building libxslt-1.1.34
Hi all I am stuck at building libxslt-1.1.34, getting the following error: I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd doc/xsltproc.xml:8: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; ]> For the record, the URL "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; works fine with curl or the browser. While I first ignored this error, it now really bites mime at shared-mime-info. I have installed both docbook-xml-4.5 and docbook-xsl-1.79.2, and also libxml2, but not any other docbook stuff. Does anybody know where this error is coming from? Bye Tim -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
