On Sat, May 31, 2014 at 10:11:07AM -0400 I heard the voice of Stefan Monnier, and lo! it spake thus: > > If you throw the error during "make", I (as a user) start wondering > "what could manpath have to do with it? Does it need to find some > man page to decide which compilation switch to use, or what?", so it > won't occur to me to pass the "destination manpath" but instead I'll > try to provide some of the system's manpath (to which I probably > don't have write access).
Well, technically, it's throwing the error during "./configure" (the less immoral equivalent thereof) here. I've pushed up some changes to adjust the process a little. I've changed it to just assume the existence of the base 'man' dir in the various places (xref below) is sufficient rather than looking for the man/man1 subdir, and rewrote the error message a little so it's hopefully a little more clear. Still. I'm surprised it seems to be failing so often. Maybe I'm just being dumber than usual. It looks (looked, before the above) for a 'man1' dir in $PREFIX/share/man and $PREFIX/man, and figures that's where you want stuff. I almost didn't even add a manual specifier since I figured that would always be there (unless things were so messed up you didn't need to be building a WM). I have a hard time coming up with a non-pathological case where that would fail, but obviously it is (for both you and Aaron!), which I'm gonna need a little help understanding. This aside from your particular "I'm not installing, so it doesn't matter" case. I'll have to see what I can come up with for that as well, but still; failing to figure the path itself Should Be such an extraordinary situation that you shouldn't ever run into the question... > I can agree that the error should be signaled before starting to install > other files Not quite trivial, with the way it all works. Maybe I can inject an extra dependancy on the install target to do it... -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
