mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <ak@suse.de>,
	kernel-janitors@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [KJ] make pdfdocs broken in 2.6.19rc2 and needs fixes
Date: Mon, 23 Oct 2006 08:49:30 -0700	[thread overview]
Message-ID: <20061023084930.8d33a996.rdunlap@xenotime.net> (raw)
In-Reply-To: <1161601779.19388.20.camel@localhost.localdomain>

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

      reply	other threads:[~2006-10-23 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22 21:47 Andi Kleen
2006-10-22 22:00 ` Jeff Garzik
2006-10-22 22:16   ` Randy Dunlap
2006-10-22 22:30     ` [KJ] " Randy Dunlap
2006-10-22 22:17   ` Andi Kleen
2006-10-23 11:09 ` Alan Cox
2006-10-23 15:49   ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061023084930.8d33a996.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kernel-janitors@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®