Date: Mon, 20 May 2002 09:13:32 +0200 From: Szilveszter Adam <sziszi@bsd.hu> To: cvs-all@FreeBSD.ORG Subject: Re: World breakage (was: cvs commit: src/share/doc/psd/03.iosys Makefile iosys) Message-ID: <20020520071332.GA607@fonix.adamsfamily.xx> In-Reply-To: <20020520110840.O54769@wantadilla.lemis.com> References: <200205190603.g4J636l46087@freefall.freebsd.org> <20020519165158.A88638-100000@patrocles.silby.com> <20020520110840.O54769@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Mon, May 20, 2002 at 11:08:40AM +0930, Greg 'groggy' Lehey wrote: > On Sunday, 19 May 2002 at 16:52:40 -0500, Mike Silbersack wrote: <...> > > ===> share/doc/psd/03.iosys > > groff -ms iosys > paper.ps > > troff: fatal error: can't open `iosys': No such file or directory > > *** Error code 1 > > > > /me frowns at the broken buildworld. > > This is really puzzling. Of course I tried a build before I committed > all this stuff, notably the top-level Makefile. There seem to be > three differing views about what was broken: <..> In my opinion, save for psd/17.m4, which was broken in the way you described, the others were a casualty of not building them in obj dirs, in a manner similar to "world". Your Makefiles had custom targets that completely disabled the infrastructure in bsd.doc.mk, so they only could work if you did not use separate obj dirs. I do not think that they were tested with "make obj && make && make install" were they? All I had to do (and I tried to explain this in my previous email, but there was no reaction to that so I assumed there was no interest) was to actually delete all the custom targets and let bsd.doc.mk do its job. I added USE_TBL=yes and USE_REFER=yes and USE_PIC=yes where appropriate and the docs built fine, except for a bunch of warnings from refer, but you said there were warnings and so I ignored them. The resultant output looks ok to me with zmore. I managed to build all of the docs, save for 17.m4 in this way. As for installation, that was a bit funky, I admit, because you neglected to update the /etc/mtree/BSD.usr.dist file with the new directories (and I did not catch it either) and therefore the files were installed as eg "01.cacm" instead of 01.cacm/paper.ascii.gz. But this was again easy to fix and could have been avoided by going with the previous examples that are already in the tree. > I've committed some patches from mark, which probably allow things to > build. They ignore references to refer, though, so we end up with > even more warnings. There's also the issue of formats: I consider the > typeset version of the documents to be the canonical one, and while we > shouldn't install that on the system, I think it should be built. The > current method is not very clean IMO. When I set the PRINTERDEVICE to "ps", a valid PS representation of the docs was built, only these are not the default. So, I think that instead of providing custom and overriding targets in your Makefiles (which, btw, included invoking "spell", although that one surely is not part of the base and even a custom "clean" target) the bsd.doc.mk infrastructure should be improved in such a way that you can specify something like: PRINTERDEVICE= ps ascii and then both will be built. This is not possible at present, but it should not be a big deal. Maybe even I can submit a patch. The docs infrastructure does something similar already, so it is probably just a matter of BACnP (Brain-Aided Copy'n'Pasting). Or did you understand something else under "typeset version"? -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020520071332.GA607>