1:40 p.m.
I grabbed kernel-doc, but it doesn't have built docs.
I grabbed kernel-docs noarch rpm from opensuse and installed that. Has man
pages (and pdfs) all built.
I wish Fedora had this.
2:28 p.m.
On 24/03/2008, Neal Becker <ndbecker2(a)gmail.com> wrote:
I grabbed kernel-doc, but it doesn't have built docs.
I grabbed kernel-docs noarch rpm from opensuse and installed that. Has man
pages (and pdfs) all built.
I wish Fedora had this.
Check under /usr/share/docs/kernel-$version - with kernel-docs
installed there is more than enough to keep me occupied.
Cheers
--
Christopher Brown
http://www.chruz.com
2:35 p.m.
On Mon, Mar 24, 2008 at 07:28:48PM +0000, Christopher Brown wrote:
On 24/03/2008, Neal Becker <ndbecker2(a)gmail.com> wrote:
> I grabbed kernel-doc, but it doesn't have built docs.
>
> I grabbed kernel-docs noarch rpm from opensuse and installed that. Has man
> pages (and pdfs) all built.
>
> I wish Fedora had this.
Check under /usr/share/docs/kernel-$version - with kernel-docs
installed there is more than enough to keep me occupied.
There's potentially a load more that we could provide. The kernel source itself
has markup in it which tools can extract into more readable format, giving you
a nice API guide. As mentioned in my other mail though, the tools suck.
Dave
--
http://www.codemonkey.org.uk
2:34 p.m.
On Mon, Mar 24, 2008 at 02:40:06PM -0400, Neal Becker wrote:
I grabbed kernel-doc, but it doesn't have built docs.
I grabbed kernel-docs noarch rpm from opensuse and installed that. Has man
pages (and pdfs) all built.
I wish Fedora had this.
This has been sitting (fairly low) on my todo list for a lon gtime.
The main thing that's put it off from happening is that every time I've
looked into it, the build has failed. It seems the tools are
fairly fragile, and don't cope too well with badly formed source.
Upstream pokes at it every so often, so the breakage tends to be
different every time I look.
The manpages seems trivial. I'll see if I can get that done today.
The pdf tools are a nightmare.
I've no idea how suse managed to get that to reliably build.
Here's what happens when I 'make pdfdocs' today..
Overfull \hbox (44.30264pt too wide) in paragraph at lines 579--582
[]\T1/ptm/m/n/10 You can tell you are in a softirq (or tasklet) us-ing the []\
T1/pcr/m/n/10 in_softirq()[] \T1/ptm/m/n/10 macro ([]\T1/pcr/m/n/10 include/lin
ux/interrupt.h[]\T1/ptm/m/n/10 ).
[3] [4] [5] [6]
! Argument of \XML@getattrib has an extra }.
<inserted text>
\par
l.870 </fo:marker>
<fo:block font-size="20.736pt">
?
! Emergency stop.
<inserted text>
\par
l.870 </fo:marker>
<fo:block font-size="20.736pt">
! ==> Fatal error occurred, the output PDF file is not finished!
What the *hell* does that even mean ?
(And you can pretty much guarantee this isn't the only error).
Dave
--
http://www.codemonkey.org.uk
3:42 p.m.
Dave Jones wrote:
Overfull \hbox (44.30264pt too wide) in paragraph at lines 579--582
[]\T1/ptm/m/n/10 You can tell you are in a softirq (or tasklet) us-ing the []\
T1/pcr/m/n/10 in_softirq()[] \T1/ptm/m/n/10 macro ([]\T1/pcr/m/n/10 include/lin
ux/interrupt.h[]\T1/ptm/m/n/10 ).
[3] [4] [5] [6]
According to the following line...
! Argument of \XML@getattrib has an extra }.
<inserted text>
\par
l.870 </fo:marker>
<fo:block font-size="20.736pt">
?
! Emergency stop.
<inserted text>
\par
l.870 </fo:marker>
<fo:block font-size="20.736pt">
! ==> Fatal error occurred, the output PDF file is not finished!
What the *hell* does that even mean ?
...it probably means this ugly kind of problems:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace
:(
Milos
8:22 p.m.
On Mon, Mar 24, 2008 at 03:34:36PM -0400, Dave Jones wrote:
> I grabbed kernel-docs noarch rpm from opensuse and installed
that. Has man
> pages (and pdfs) all built.
>
> I wish Fedora had this.
This has been sitting (fairly low) on my todo list for a lon gtime.
The main thing that's put it off from happening is that every time I've
looked into it, the build has failed. It seems the tools are
fairly fragile, and don't cope too well with badly formed source.
Upstream pokes at it every so often, so the breakage tends to be
different every time I look.
The manpages seems trivial. I'll see if I can get that done today.
Done. Will be in tomorrows build.
The pdf tools are a nightmare.
I've no idea how suse managed to get that to reliably build.
I tried to find out how suse managed to pull this off.
After quite a bit of hunting around, I drew a blank as to how
exactly the kernel-docs rpm is created. If you know where they
keep the srpm (or spm as they seem to call them, those crazy germans)
I'll check it out and see if we can maybe get the pdfs built too.
I looked in the kernel-source package, which would be the logical
place to build it from, but it seems that it comes from elsewhere.
Dave
--
http://www.codemonkey.org.uk
2:08 a.m.
Am Montag, den 24.03.2008, 21:22 -0400 schrieb Dave Jones:
I tried to find out how suse managed to pull this off.
After quite a bit of hunting around, I drew a blank as to how
exactly the kernel-docs rpm is created. If you know where they
keep the srpm (or spm as they seem to call them, those crazy germans)
I'll check it out and see if we can maybe get the pdfs built too.
I looked in the kernel-source package, which would be the logical
place to build it from, but it seems that it comes from elsewhere.
Try that one...
ftp://mirrors.kernel.org/opensuse/distribution/SL-OSS-factory/inst-source...
-- Frank
(not all Germans are crazy, but quite a few)
10:37 a.m.
On Tue, Mar 25, 2008 at 08:08:50AM +0100, Frank Arnold wrote:
Am Montag, den 24.03.2008, 21:22 -0400 schrieb Dave Jones:
> I tried to find out how suse managed to pull this off.
> After quite a bit of hunting around, I drew a blank as to how
> exactly the kernel-docs rpm is created. If you know where they
> keep the srpm (or spm as they seem to call them, those crazy germans)
> I'll check it out and see if we can maybe get the pdfs built too.
> I looked in the kernel-source package, which would be the logical
> place to build it from, but it seems that it comes from elsewhere.
Try that one...
ftp://mirrors.kernel.org/opensuse/distribution/SL-OSS-factory/inst-source...
Thanks. The specfile does a little magic to adjust a few limits.
http://marc.info/?l=linux-doc&m=120642969729883&w=2 also has some info,
which mentions that some changes to TeX are needed.
I'm not sure if the limit changes the specfile does are enough, or
if TeX will need patching. I'll experiment a little this afternoon.
-- Frank
(not all Germans are crazy, but quite a few)
heh :)
Dave
--
http://www.codemonkey.org.uk
5883
days inactive
5884
days old
7 comments
5 participants
participants (5)
-
Christopher Brown -
Dave Jones -
Frank Arnold -
Milos Jakubicek -
Neal Becker