[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] [bug-wget] pod problems when compiling, with perl 5.18
From: |
Tim Rühsen |
Subject: |
Re: [Bug-wget] [bug-wget] pod problems when compiling, with perl 5.18 |
Date: |
Sun, 26 May 2013 21:27:54 +0200 |
User-agent: |
KMail/1.13.7 (Linux/3.8-2-amd64; KDE/4.8.4; x86_64; ; ) |
Am Sonntag, 26. Mai 2013 schrieb Javier Vasquez:
> On Sun, May 26, 2013 at 9:51 AM, Tim Rühsen <address@hidden> wrote:
> > ...
> >
> > You can edit wget.texi and change all e.g. '@item <number>' into '@item
> > <string>. I can't test it right here since perl 5.18 is still in
experimental
> > and has some dependancy problems right now.
> >
> > So, this is just an example patch, that should correct the issues with
perl
> > numbers. Not shure how e.g. @item '1' would appear in the man page, so I
take
> > @item 1..
> >
> >...
> >
> > Regards, Tim
>
> That was really helpful Tim, made me look into texinfo documentation...
>
> The dot, ".", after the number didn't help, I had to place it before
> instead, :-).
>
> Also if one has @item in the immediate following line after another
> @item, that's a failure, since texinfo requires @itemx instead.
>
> And even one has @item followed by @itemx, but with other lines in
> between the 2, somehow that's not understood, and @item is required...
>
> Weird thing...
>
> I'm attaching the patch that worked for me, and I'm pasting how the
> man looks like for the particular exit status after the fix:
>
> ++++++++++++++++++++++++
> EXIT STATUS
> Wget may return one of several error codes if it encounters problems.
>
> .0 No problems occurred.
>
> .1 Generic error code.
>
> .2 Parse error - for instance, when parsing command-line
> options, the .wgetrc or .netrc...
>
> .3 File I/O error.
>
> .4 Network failure.
>
> .5 SSL verification failure.
>
> .6 Username/password authentication failure.
>
> .7 Protocol errors.
>
> .8 Server issued an error response.
> ++++++++++++++++++++++++
>
> Well, it's able to build now, :-)
>
> --
> Javier.
>
Thanks, that's good to hear.
Could you give a try for "1" or '1' instead of .1 ?
I wonder if that compiles and how it looks in the man page...
IF it works and looks good, maybe you could attach a new patch !?
Regards, Tim