You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-dev@perl.apache.org by Per Einar Ellefsen <pe...@skynet.be> on 2002/03/27 22:06:08 UTC
build errors
Hi all,
I'm running Cygwin under Windows XP. Wanting to build the site, I got
DocSet and all its prerequisites (btw Stas, you need to update the README,
it doesn't state Template and Pod::POM as prereqs).
But I'm having some big problems:
running:
$ bin/build
I get this output:
html2ps: Command not found. (is this a problem ?)
----------------------------------------
File:
/cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/maillist/email-etiquette.pod
spurious '>' at <input text> line 11
spurious '>' at <input text> line 400
spurious '>' at <input text> line 400
spurious '>' at <input text> line 400
spurious '>' at <input text> line 404
----------------------------------------
File:
/cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/docs/1.0/guide/intro.pod
spurious '>' at <input text> line 66
spurious '>' at <input text> line 71
...
Actually, it seems like it barks at all the HTML tags in the =for html POD
parts.
I'm not sure why it's complaining about this, as I know they're supposed to
be there.
I get my dst_html directory, but all the pages generated from POD files
don't appear, not even their titles.
So.. problem..
Anyone know what is causing this?
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 04:57 05.04.2002, Stas Bekman wrote:
>Per Einar Ellefsen wrote:
>>Ok, stupid me: I removed the second part from the test Pod, and now it
>>worked. So everything's ok with Pod::POM (well, not everything, =begin
>>html doesn't work, but as you said, we had a problem with =for).
>
>Hmm, let's put the second sub-test aside. You reported earlier problems
>with '=for html <...' did they gone now?
I told you, that was using Cygwin (a Unix layer running on top of Win32).
When using Win32 standard shell with ActiveState Perl I have no problems.
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Stas Bekman <st...@stason.org>.
Per Einar Ellefsen wrote:
> At 20:06 04.04.2002, Per Einar Ellefsen wrote:
>
>> At 09:39 03.04.2002, Stas Bekman wrote:
>>
>>> Per Einar Ellefsen wrote:
>>> notice that there are two sub-tests here, the second one does fail
>>> for me and it shouldn't. but in our case the problem is with '=for html'
>>
>>
>> And it runs ok without the patch. So yes, I assume this is a Pod::POM
>> problem. It should be valid Pod. I'm not sure if it actually fails for
>> the first or the second test though, how do I know?
>
>
> Ok, stupid me: I removed the second part from the test Pod, and now it
> worked. So everything's ok with Pod::POM (well, not everything, =begin
> html doesn't work, but as you said, we had a problem with =for).
Hmm, let's put the second sub-test aside. You reported earlier problems
with '=for html <...' did they gone now?
it could be that the =begin/=end syntax is simply not implemented. I'll
look into it, but we don't use it now anyway.
--
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 20:06 04.04.2002, Per Einar Ellefsen wrote:
>At 09:39 03.04.2002, Stas Bekman wrote:
>>Per Einar Ellefsen wrote:
>>notice that there are two sub-tests here, the second one does fail for me
>>and it shouldn't. but in our case the problem is with '=for html'
>
>And it runs ok without the patch. So yes, I assume this is a Pod::POM
>problem. It should be valid Pod. I'm not sure if it actually fails for the
>first or the second test though, how do I know?
Ok, stupid me: I removed the second part from the test Pod, and now it
worked. So everything's ok with Pod::POM (well, not everything, =begin html
doesn't work, but as you said, we had a problem with =for).
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 09:39 03.04.2002, Stas Bekman wrote:
>Per Einar Ellefsen wrote:
>
>I've merged your patches, let me know if this works now. Do you get the
>site properly built now?
Well, these errors were for Cygwin.
I'm not getting them anymore with Win32. And yes, I can build my site
correctly. So everything is fine. I still tested what you told me to though.
>ok, it seems like this is a Pod::POM problem, please test if this test
>patch triggers this problem?
>
>--- t/warn.t.orig Wed Apr 3 15:32:14 2002
>+++ t/warn.t Wed Apr 3 15:37:12 2002
>@@ -106,3 +106,14 @@
> >oh dear!
>
> Blah > Blah
>+
>+=for html <a href=""><b>no warnings</b></a>
>+<i>at all</i>
>+
>+=begin html
>+
>+<!--
>+no warnings expected here either
>+-->
>+
>+=end
>
>notice that there are two sub-tests here, the second one does fail for me
>and it shouldn't. but in our case the problem is with '=for html'
t\code..............ok
t\complete..........ok
t\head..............ok
t\htmlescp..........ok
t\htmllist..........ok
t\htmlview..........ok
t\list..............ok
t\meta..............ok
t\text..............ok
t\textview..........ok
t\view..............ok
t\warn..............FAILED tests 2, 10-11, 26-27
Failed 5/27 tests, 81.48% okay
t\wrap..............ok
Failed Test Status Wstat Total Fail Failed List of Failed
--------------------------------------------------------------------------------
t\warn.t 27 5 18.52% 2, 10-11, 26-27
And it runs ok without the patch. So yes, I assume this is a Pod::POM
problem. It should be valid Pod. I'm not sure if it actually fails for the
first or the second test though, how do I know?
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Stas Bekman <st...@stason.org>.
Per Einar Ellefsen wrote:
I've merged your patches, let me know if this works now. Do you get the
site properly built now?
also see below
>>> ----------------------------------------
>>> File:
>>> /cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/maillist/email-etiquette.pod
>>>
>>> spurious '>' at <input text> line 11
>>> spurious '>' at <input text> line 400
>>> spurious '>' at <input text> line 400
>>> spurious '>' at <input text> line 400
>>> spurious '>' at <input text> line 404
>>> ----------------------------------------
>>> File:
>>> /cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/docs/1.0/guide/intro.pod
>>>
>>> spurious '>' at <input text> line 66
>>> spurious '>' at <input text> line 71
>>
>>
>> This is a bad POD, I'll fix those. (unescaped '>' and '<')
>>
>>> ...
>>> Actually, it seems like it barks at all the HTML tags in the =for
>>> html POD parts.
>>> I'm not sure why it's complaining about this, as I know they're
>>> supposed to be there.
>>
>>
>> see above
>> No, actually this is not a bad POD, as you said the first one is
>> inside html block so any mark up should be ignored.
>> The second is code block and the same should apply. I don't get these
>> problems reported, do you run the latest Pod::POM?
>> v0.15?
>
>
> Yes, I have Pod::POM v. 0.15. Didn't show up using $Pod::POM::VERSION,
> but I checked the build directory, and it said 0.15 in it. I installed
> it directyl with the CPAN shell yesterday, so it should be the latest.
ok, it seems like this is a Pod::POM problem, please test if this test
patch triggers this problem?
--- t/warn.t.orig Wed Apr 3 15:32:14 2002
+++ t/warn.t Wed Apr 3 15:37:12 2002
@@ -106,3 +106,14 @@
>oh dear!
Blah > Blah
+
+=for html <a href=""><b>no warnings</b></a>
+<i>at all</i>
+
+=begin html
+
+<!--
+no warnings expected here either
+-->
+
+=end
notice that there are two sub-tests here, the second one does fail for
me and it shouldn't. but in our case the problem is with '=for html'
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 02:40 28.03.2002, Stas Bekman wrote:
>Per Einar Ellefsen wrote:
>>Hi all,
>>I'm running Cygwin under Windows XP. Wanting to build the site, I got
>>DocSet and all its prerequisites (btw Stas, you need to update the
>>README, it doesn't state Template and Pod::POM as prereqs).
>
>No, these are the prerequisites of DocSet, I cannot recursively list all
>the prerequisites. When you run 'perl Makefile.PL' it checks the
>prerequisites and reports misses. Does it for you?
Well, I was talking about the DocSet package :)
Anyway, no problem, it listed the prerequisites I needed when I ran `perl
Makefile.PL`
>>But I'm having some big problems:
>>running:
>>$ bin/build
>>I get this output:
>>html2ps: Command not found. (is this a problem ?)
>
>you won't be able to build the pdfs without this (which is needed when you
>use -d flag to bin/build). It goes like this:
>
>DocSet installs html2ps, then when it's run it checks whether it has
>html2ps by calling system('which html2ps'). Now I've no idea whether
>which() works on non-Unix systems. Please look at the
>lib/DocSet/RunTime.pm and see if there is a better crossplatform solution
>for checking whether some executable is available.
Wow, weird. When I run which html2ps, I get "html2ps: Command not found"
However, html2ps is installed, and I can run it. Very weird. Must be a
cygwin bug, and I can't reproduce it with anything else.
Anyway, this isn't your problem, and it doesn't matter so much to me if I
don't get the PDF versions.
Concerning which: I'm not running this straight on Win32, I'm running it
under cygwin, a Unix emulation layer, so it's closer to Unix. which clearly
doesn't work on Win32, and I didn't even want to try running DocSet on
stock Win32, as I'd probably run into a lot of obscure errors (like not
even being able to run bin/build because it uses the "env" command which
isn't available on Win32). I don't know about any cross-platform module,
the only way I can think of is just to emulate the whole thing in Perl. Is
it worth it? Should I try and get DocSet working on standard Win32?
>Next step it checks whether you have ps2pdf(1) which is needed to convert
>PS files to PDFs. It uses the same technique.
I've got that one too, but as it doesn't find html2ps using which, there's
no point in this :)
>>----------------------------------------
>>File:
>>/cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/maillist/email-etiquette.pod
>>
>>spurious '>' at <input text> line 11
>>spurious '>' at <input text> line 400
>>spurious '>' at <input text> line 400
>>spurious '>' at <input text> line 400
>>spurious '>' at <input text> line 404
>>----------------------------------------
>>File:
>>/cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/docs/1.0/guide/intro.pod
>>spurious '>' at <input text> line 66
>>spurious '>' at <input text> line 71
>
>This is a bad POD, I'll fix those. (unescaped '>' and '<')
>
>>...
>>Actually, it seems like it barks at all the HTML tags in the =for html
>>POD parts.
>>I'm not sure why it's complaining about this, as I know they're supposed
>>to be there.
>
>see above
>No, actually this is not a bad POD, as you said the first one is inside
>html block so any mark up should be ignored.
>The second is code block and the same should apply. I don't get these
>problems reported, do you run the latest Pod::POM?
>v0.15?
Yes, I have Pod::POM v. 0.15. Didn't show up using $Pod::POM::VERSION, but
I checked the build directory, and it said 0.15 in it. I installed it
directyl with the CPAN shell yesterday, so it should be the latest.
>>I get my dst_html directory, but all the pages generated from POD files
>>don't appear, not even their titles.
>>So.. problem..
>
>none of the problems you've mentioned so far, should be a critical problem
>for getting the basic site build.
Well the basic site is built. But as I mentioned, I get:
- all documents created from POD sources are empty
- no titles or descriptions on the pages listing these documents.
This is very weird, and I can only assume it's caused by some malfunction
of the interpretation of the POD documents.
>>Anyone know what is causing this?
>
>DocSet was developed on Linux and tested on a few Unix platforms.
>It's quite possible that some tweaks are needed for other platforms,
>but you will need to help me here.
If I found out what was wrong, I would :) Anyway, as I said above, Cygwin
is pretty close to Unix...
>The verbose mode shows almost everything the DocSet does, so simple add -v
>flag:
>
> bin/build -vf
>
>see what it attempts to do and check that it actually does this. Could be
>that more checks need to be added. If all this doesn't help, try to work
>with the perl debugger.
Well, everything seems pretty normal to me... I'm not sure what is supposed
to happen, but I get for example this on the Downloads part:
####################################
### [scan] HTML DocSet: Download ###
####################################
+++ Reading cache from
/cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/download/cache.html.dat
+++ source.pod: processing (not modified / forced)
+++ Scanning source.pod
+++ binaries.pod: processing (not modified / forced)
+++ Scanning binaries.pod
+++ bundles.html: processing (not modified / forced)
+++ Scanning bundles.html
+++ Storing the docset's cache to
/cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/download/cache.html.dat
I'll maybe have to try with the pelr debugger, yes...
>I really hope that it won't be hard to make it work on non-Unix platforms.
>
>p.s. I'm leaving for a long weekend today, so may be others will be able
>to help here while I'm away.
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 06:47 29.03.2002, Randy Kobes wrote:
>On Thu, 28 Mar 2002, Stas Bekman wrote:
>
> > Per Einar Ellefsen wrote:
> >
> > > But I'm having some big problems:
> > > running:
> > > $ bin/build
> > >
> > > I get this output:
> > >
> > > html2ps: Command not found. (is this a problem ?)
> >
> > you won't be able to build the pdfs without this (which is needed when
> > you use -d flag to bin/build). It goes like this:
> >
> > DocSet installs html2ps, then when it's run it checks whether it has
> > html2ps by calling system('which html2ps'). Now I've no idea whether
> > which() works on non-Unix systems. Please look at the
> > lib/DocSet/RunTime.pm and see if there is a better crossplatform
> > solution for checking whether some executable is available.
>
>A portable "which" is in modperl-2.0/lib/Apache/Build.pm.
Aah, nice Randy!
I think I'll actually go for trying to port DocSet to Windows, it'll allow
me to debug more easily.
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
> Per Einar Ellefsen wrote:
>> ----------------------------------------
>> File:
>> /cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/maillist/email-etiquette.pod
>>
>> spurious '>' at <input text> line 11
>> spurious '>' at <input text> line 400
>> spurious '>' at <input text> line 400
>> spurious '>' at <input text> line 400
>> spurious '>' at <input text> line 404
>>
>> ----------------------------------------
>> File:
>> /cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/docs/1.0/guide/intro.pod
>>
>> spurious '>' at <input text> line 66
>> spurious '>' at <input text> line 71
>
>
> This is a bad POD, I'll fix those. (unescaped '>' and '<')
No, actually this is not a bad POD, as you said the first one is inside
html block so any mark up should be ignored.
The second is code block and the same should apply. I don't get these
problems reported, do you run the latest Pod::POM?
v0.15?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Thu, 28 Mar 2002, Stas Bekman wrote:
> Per Einar Ellefsen wrote:
>
> > But I'm having some big problems:
> > running:
> > $ bin/build
> >
> > I get this output:
> >
> > html2ps: Command not found. (is this a problem ?)
>
> you won't be able to build the pdfs without this (which is needed when
> you use -d flag to bin/build). It goes like this:
>
> DocSet installs html2ps, then when it's run it checks whether it has
> html2ps by calling system('which html2ps'). Now I've no idea whether
> which() works on non-Unix systems. Please look at the
> lib/DocSet/RunTime.pm and see if there is a better crossplatform
> solution for checking whether some executable is available.
A portable "which" is in modperl-2.0/lib/Apache/Build.pm.
best regards,
randy kobes
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: build errors
Posted by Stas Bekman <st...@stason.org>.
Per Einar Ellefsen wrote:
>
> Hi all,
>
> I'm running Cygwin under Windows XP. Wanting to build the site, I got
> DocSet and all its prerequisites (btw Stas, you need to update the
> README, it doesn't state Template and Pod::POM as prereqs).
No, these are the prerequisites of DocSet, I cannot recursively list all
the prerequisites. When you run 'perl Makefile.PL' it checks the
prerequisites and reports misses. Does it for you?
> But I'm having some big problems:
> running:
> $ bin/build
>
> I get this output:
>
> html2ps: Command not found. (is this a problem ?)
you won't be able to build the pdfs without this (which is needed when
you use -d flag to bin/build). It goes like this:
DocSet installs html2ps, then when it's run it checks whether it has
html2ps by calling system('which html2ps'). Now I've no idea whether
which() works on non-Unix systems. Please look at the
lib/DocSet/RunTime.pm and see if there is a better crossplatform
solution for checking whether some executable is available.
Next step it checks whether you have ps2pdf(1) which is needed to
convert PS files to PDFs. It uses the same technique.
> ----------------------------------------
> File:
> /cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/maillist/email-etiquette.pod
>
> spurious '>' at <input text> line 11
> spurious '>' at <input text> line 400
> spurious '>' at <input text> line 400
> spurious '>' at <input text> line 400
> spurious '>' at <input text> line 404
>
> ----------------------------------------
> File:
> /cygdrive/d/users/pereinar/mod-perl/modperl-docs/src/docs/1.0/guide/intro.pod
>
> spurious '>' at <input text> line 66
> spurious '>' at <input text> line 71
This is a bad POD, I'll fix those. (unescaped '>' and '<')
> ...
> Actually, it seems like it barks at all the HTML tags in the =for html
> POD parts.
> I'm not sure why it's complaining about this, as I know they're supposed
> to be there.
see above
> I get my dst_html directory, but all the pages generated from POD files
> don't appear, not even their titles.
> So.. problem..
none of the problems you've mentioned so far, should be a critical
problem for getting the basic site build.
> Anyone know what is causing this?
DocSet was developed on Linux and tested on a few Unix platforms.
It's quite possible that some tweaks are needed for other platforms,
but you will need to help me here.
The verbose mode shows almost everything the DocSet does, so simple add
-v flag:
bin/build -vf
see what it attempts to do and check that it actually does this. Could
be that more checks need to be added. If all this doesn't help, try to
work with the perl debugger.
I really hope that it won't be hard to make it work on non-Unix platforms.
p.s. I'm leaving for a long weekend today, so may be others will be able
to help here while I'm away.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org