From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: Brian.Inglis@Shaw.ca, Linux Man-Pages <linux-man@vger.kernel.org>
Cc: Deri <deri@chuzzlewit.myzen.co.uk>
Subject: Re: man-pages-posix: POSIX book build
Date: Sun, 13 Aug 2023 23:17:51 +0200 [thread overview]
Message-ID: <8d46f1e0-9e8a-5c65-3f13-e935445c5742@gmail.com> (raw)
In-Reply-To: <4c6d1cd6-7b25-2818-108d-5af7afaa9680@Shaw.ca>
[-- Attachment #1.1.1: Type: text/plain, Size: 1669 bytes --]
Hi Brian,
On 2023-08-13 23:04, Brian Inglis wrote:
> Hi folks,
>
> Just to see if making a POSIX book works, I copied 1.23.0 LinuxManBook as
> PosixManBook, BuildLinuxMan.pl to BuildPosixMan.pl, LMBfront.t to PMBfront.t
> with content changes, added sections "[013]p" and made other obvious perl script
> edits '%s/Linux/Posix/g', '%s/LMB/PMB/g'.
>
> When I ran the perl script, eqn was growing into the GB memory, and eqn and
> troff were each hogging a cpu, so I left it running while we were out at dinner
> with friends, but *eqn* died after apparently exhausting all memory and using
> 48GB page space, getting as far as limits.h(0p) for a 57 page PDF!
Huh!
If you want to tinker with the Linux man-pages Makefile, it may be useful to your
experiment.
$ # run the following from the root of the Linux man-pages repository.
$ make -kj lint build check MANDIR=../../man-pages-posix/man-pages-posix-2017/
This works. It gets many warnings, of course, but it builds PDF files of every
page, among PS, HTML, and a lot more stuff. You may be able to tweak the
makefiles to build a book. If you get to that, please send the patches =)
I attached one of the pages (from man-pages-posix-2003). (Oh boy, did I ever
mention that I like bzero(3)? :D).
As mentioned recently in the list, you can use the Linux man-pages Makefile to
lint and build PDF, PS, and HTML pages of every project (or at least of every
project I tried). If any project fails, I'm interested in making it work, so
please report.
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #1.1.2: bzero.3p.pdf --]
[-- Type: application/pdf, Size: 20743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-13 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 21:04 man-pages-posix: POSIX book build Brian Inglis
2023-08-13 21:17 ` Alejandro Colomar [this message]
2023-08-13 22:29 ` G. Branden Robinson
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=8d46f1e0-9e8a-5c65-3f13-e935445c5742@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=Brian.Inglis@Shaw.ca \
--cc=alx@kernel.org \
--cc=deri@chuzzlewit.myzen.co.uk \
--cc=linux-man@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