From: Andi Kleen <ak@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@lists.osdl.org
Subject: Re: make pdfdocs broken in 2.6.19rc2 and needs fixes
Date: Mon, 23 Oct 2006 00:17:42 +0200 [thread overview]
Message-ID: <200610230017.42614.ak@suse.de> (raw)
In-Reply-To: <453BEA00.4000601@garzik.org>
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
next prev parent reply other threads:[~2006-10-22 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 21:47 make pdfdocs broken in 2.6.19rc2 and needs fixes 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 [this message]
2006-10-23 11:09 ` Alan Cox
2006-10-23 15:49 ` [KJ] " Randy Dunlap
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=200610230017.42614.ak@suse.de \
--to=ak@suse.de \
--cc=jeff@garzik.org \
--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