Hi Richard

Sorry about that. This would be one of the reasons why I am
refactoring this stuff.
Its pain-the-... as it is now.

You have three options:
a) Try again (I added the missing files)
b) Rollback to docbook_xsl_1_68_1
c) Wait a little while longer until I am finished.

I'd appreciate if you try option "a" for me. I prefer to leave the
updated-but-not-refactored build working if, for what ever reason, we
need to go back.

-Hannes

On 1/22/07, Richard A. Quadling <[EMAIL PROTECTED]> wrote:
./make chm_xsl is failing.

This is the output for this command.

rm -rf ./htmlhelp/html && mkdir ./htmlhelp/html && mkdir
htmlhelp/html/figures
cp ./en/internals/zendapi/figures/*.png ./htmlhelp/html/figures
/usr/bin/xsltproc xsl/htmlhelp.xsl manual.xml
warning: failed to load external entity
"xsl/docbook/highlighting/common.xsl"
compilation error: file xsl/docbook/html/verbatim.xsl line 20 element
include
xsl:include : unable to load xsl/docbook/highlighting/common.xsl
make: *** [chm_xsl] Error 5

Prior to this I run ...

autoconf -v -d --warnings=all &> $HOME/autoconf.log
./configure --with-source=./../php-src --with-pear-source=./../pear
--with-chm=yes --with-treesaving &> $HOME/configure.log
make test &> $HOME/make_test.log
make test_xml &> $HOME/make_test_xml.log
make chm_xsl &> $HOME/make_chm_xsl.log

And then more happens to construct the Windows CHM file. Normally this
process takes me an hour and has been working for me for a while now.

I think the highlighting xsl code is missing as there is no
xsl/docbook/highlighting folder in CVS.

This was added recently (just over an hour ago) -
http://cvs.php.net/viewvc.cgi/phpdoc/xsl/docbook/html/verbatim.xsl?r1=1.
4&r2=1.5

I assume this is coming (or will be when bjori reads this! :-) ).


From the xsl/docbook/RELEASE-NOTES.txt, I can see that the source of the
for hightlighting is available
(http://xmlguru.cz/2006/07/docbook-syntax-highlighting). Is this
intended to be a manual installation or will this become part of the cvs
for phpdoc?


Regards,

Richard Quadling.

Reply via email to