Jim Winstead wrote:
it is broken because the system builds the manual outside of the phpdoc
tree. that means when $(srcdir) isn't properly used, the build breaks.
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's configure from there (using
en/build.log:
sed: can't read confdefs.h: No such file or directory
running make test_man_gen ...
make: *** No rule to make target `test_man_gen'. Stop.
Same for translations.
slawek-
Slawomir Pucia wrote:
running make test_man_gen ...
make: *** No rule to make target `test_man_gen'. Stop.
can't reproduce this here, so i think (hope) my configure.in patch
from last night has fixed that ...
--
Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
can't reproduce this here, so i think (hope) my configure.in patch
from last night has fixed that ...
I was building manual yesterday on my box (before you submitted the patch),
and everything was ok. It seems to be broken on php.net's box for few days,
since the newest version is dated
Slawomir Pucia wrote:
can't reproduce this here, so i think (hope) my configure.in patch
from last night has fixed that ...
I was building manual yesterday on my box (before you submitted the patch),
and everything was ok. It seems to be broken on php.net's box for few days,
since the
it is broken because the system builds the manual outside of the phpdoc
tree. that means when $(srcdir) isn't properly used, the build breaks.
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's configure from there (using whatever
absolute or
Jim Winstead wrote:
it is broken because the system builds the manual outside of the phpdoc
tree. that means when $(srcdir) isn't properly used, the build breaks.
ok, blame me :(
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's
From: Jim Winstead [EMAIL PROTECTED]
it is broken because the system builds the manual outside of the
phpdoc
tree. that means when $(srcdir) isn't properly used, the build
breaks.
Ok, but there is another error in the build system or the manual
itself. Look at the PDF manuals and you will see
Egon Schmid wrote:
Ok, but there is another error in the build system or the manual
itself. Look at the PDF manuals and you will see a incomplete table
of content (?? as page numbers at the end) and this pages aren´t
shown.
most likely we have hit a TeX buffer limit once again
--
Hartmut
On Thu, Jan 10, 2002 at 06:37:09PM +0100, Hartmut Holzgraefe wrote:
Egon Schmid wrote:
Ok, but there is another error in the build system or the manual
itself. Look at the PDF manuals and you will see a incomplete table
of content (?? as page numbers at the end) and this pages aren?t
shown.
From: Hartmut Holzgraefe [EMAIL PROTECTED]
Ok, but there is another error in the build system or the manual
itself. Look at the PDF manuals and you will see a incomplete
table
of content (?? as page numbers at the end) and this pages aren´t
shown.
most likely we have hit a TeX buffer
Jim Winstead wrote:
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's configure from there (using whatever
absolute or relative path is appropriate).
how has this ever worked when some of the stylesheets (the plain
.dsl files) stay in $srcdir
ignore my previous question, i'm getting stupid :(
--
Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
From: Hartmut Holzgraefe [EMAIL PROTECTED]
most likely we have hit a TeX buffer limit once again
If you compare the translated PDF manuals you will see that:
en:Chapter 46Database issues
de:Kapitel 46Database issues
stops at the same page content on different
14 matches
Mail list logo
