"Matthew D. Fuller" <[email protected]> writes: (snip) > Blurg. This surprises me. I've never imagined a *nix system that > _didn't_ have lex and yacc installed. And now 2/3 people on this > thread have turned them up. What the heck, world? I guess I really > _do_ need to figure out how to have them prebuilt for release tarballs > (rather, how to sneak them in under cmake's nose).
They don't even have things like "units" installed, it's amazing. (-: This is mostly a stock Debian stable installation, and most of my actual development activity happens elsewhere (and with different parser libraries). (snip) > This is the hitch here; MANBASE needs to be something passed to cmake, > not something in the environment. e.g.: Aha! Well that explains it. Now it is built and I am running ctwm revision 347, so far so good. Thank you for your help. (snip) > I'm a little surprised that you'd need to specify it though, unless > /usr/local/man/man1 doesn't already exist (the process looks for > 'man1' in a couple places). /usr/share/man/ is where this system's manpages are and the local ones should go into /usr/local/share/man (to which /usr/local/man symlinks). However, I rarely want to install "local" hand-built stuff for all users so I put such few things in my home directory and at present /usr/local/share/man has nothing in it whatsoever. (snip) > In concept, I guess we could wait until the manpage install process to > throw the error. I always feel better about dying as soon as > something's known bad though; it feels unfriendly to go all through > the build, install ctwm and its files, and THEN "Oops" trying to > install the manpage, leaving you with a partial install. (snip) I'd like to be able to build without installing -- I often do to check if a bug in a packaged version of something still exists in a later version -- but I can certainly see your point. (For these development releases I'm copying the ctwm executable into my local ~/bin and naming each according to which version it is.) -- Mark
