When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
messages and then some corrupted PDFs in the end.
Fixing that (I suppose it will just need comment fixes and
should not affect the code) should be a relatively easy task for
a newbie and would be useful for the 2.6.19 release.
-Andi
Andi Kleen wrote:
> When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
> messages and then some corrupted PDFs in the end.
>
> Fixing that (I suppose it will just need comment fixes and
> should not affect the code) should be a relatively easy task for
> a newbie and would be useful for the 2.6.19 release.
What userland were you using? Unfortunately with 'make *docs' that matters.
Unquestionably, there is breakage regardless of distro.
Jeff
On Sun, 22 Oct 2006 18:00:32 -0400 Jeff Garzik wrote:
> Andi Kleen wrote:
> > When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
> > messages and then some corrupted PDFs in the end.
> >
> > Fixing that (I suppose it will just need comment fixes and
> > should not affect the code) should be a relatively easy task for
> > a newbie and would be useful for the 2.6.19 release.
>
> What userland were you using? Unfortunately with 'make *docs' that matters.
>
> Unquestionably, there is breakage regardless of distro.
I find it easier to just use/check make htmldocs && make mandocs
to look for errors and to test fixes. At least as a first pass.
---
~Randy
On Monday 23 October 2006 00:00, Jeff Garzik wrote:
> Andi Kleen wrote:
> > When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
> > messages and then some corrupted PDFs in the end.
> >
> > Fixing that (I suppose it will just need comment fixes and
> > should not affect the code) should be a relatively easy task for
> > a newbie and would be useful for the 2.6.19 release.
>
> What userland were you using? Unfortunately with 'make *docs' that matters.
>
> Unquestionably, there is breakage regardless of distro.
SUSE 10.0 userland. The errors look like pretty generic TeX errors
though and that tends to not change very often.
-Andi
On Sun, 22 Oct 2006 15:16:00 -0700 Randy Dunlap wrote:
> On Sun, 22 Oct 2006 18:00:32 -0400 Jeff Garzik wrote:
>
> > Andi Kleen wrote:
> > > When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
> > > messages and then some corrupted PDFs in the end.
> > >
> > > Fixing that (I suppose it will just need comment fixes and
> > > should not affect the code) should be a relatively easy task for
> > > a newbie and would be useful for the 2.6.19 release.
> >
> > What userland were you using? Unfortunately with 'make *docs' that matters.
> >
> > Unquestionably, there is breakage regardless of distro.
>
> I find it easier to just use/check make htmldocs && make mandocs
> to look for errors and to test fixes. At least as a first pass.
and those (htmldocs, mandocs) won't catch the errors that
Andi is seeing. :(
---
~Randy
Ar Sul, 2006-10-22 am 23:47 +0200, ysgrifennodd Andi Kleen:
> When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
> messages and then some corrupted PDFs in the end.
Some vendor shipped pdf and TeX tools are problematic. It works
correctly on Red Hat except for kernel-api which has become too big for
the default settings when ext4 was added. The TeX hash size gets
exceeded, TeX emits
"! TeX capacity exceeded, sorry [hash size=60000].
If you really absolutely need more capacity,
you can ask a wizard to enlarge me."
Really it would be nice to find a more modern way from the input to pdf
without going via tex.
On Mon, 23 Oct 2006 12:09:39 +0100 Alan Cox wrote:
> Ar Sul, 2006-10-22 am 23:47 +0200, ysgrifennodd Andi Kleen:
> > When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
> > messages and then some corrupted PDFs in the end.
>
> Some vendor shipped pdf and TeX tools are problematic. It works
> correctly on Red Hat except for kernel-api which has become too big for
> the default settings when ext4 was added. The TeX hash size gets
> exceeded, TeX emits
>
> "! TeX capacity exceeded, sorry [hash size=60000].
> If you really absolutely need more capacity,
> you can ask a wizard to enlarge me."
I have a k-doc note to self which says something like "move all
filesystems from kernel-api to filesystems-api". That was just
for compartmentalization or modularization, not to fix this tools
problem, but it would do that as well. So I can do that soon.
> Really it would be nice to find a more modern way from the input to pdf
> without going via tex.
Agreed.
I've been thinking of exploring other transform tools, but I
haven't taken the time to do that yet.
---
~Randy