All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] make pdfdocs broken in 2.6.19rc2 and needs fixes
Date: Thu, 26 Oct 2006 19:45:48 +0000	[thread overview]
Message-ID: <4541106C.7080802@bfs.de> (raw)
In-Reply-To: <200610222347.42418.ak@suse.de>



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`000].
> If you really absolutely need more capacity,
> you can ask a wizard to enlarge me."
> 


mmmh, roff supports pdf these days also ;)



> 
> Really it would be nice to find a more modern way from the input to pdf
> without going via tex.
> 
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-10-26 19:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22 21:47 [KJ] make pdfdocs broken in 2.6.19rc2 and needs fixes Andi Kleen
2006-10-22 21:47 ` Andi Kleen
2006-10-22 22:00 ` [KJ] " Jeff Garzik
2006-10-22 22:00   ` Jeff Garzik
2006-10-22 22:16   ` [KJ] " Randy Dunlap
2006-10-22 22:16     ` Randy Dunlap
2006-10-22 22:30     ` [KJ] " Randy Dunlap
2006-10-22 22:30       ` Randy Dunlap
2006-10-22 22:17   ` Andi Kleen
2006-10-22 22:17     ` Andi Kleen
2006-10-23 11:09 ` [KJ] " Alan Cox
2006-10-23 11:09   ` Alan Cox
2006-10-23 15:49   ` [KJ] " Randy Dunlap
2006-10-23 15:49     ` Randy Dunlap
2006-10-26 19:45 ` walter harms [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=4541106C.7080802@bfs.de \
    --to=wharms@bfs.de \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.