man cc
=>
cc: Native C compiler not found
and then a "wierd" interaction that is probably more on a big empty file or
something.
I understand -- My configuration is wierd such that setup didn't find Visual
C++, and man doesn't have separate text files but runs the command with some
switch, and that command in this case "configures itself" before handling that
switch.
Perhaps the handling of the man switch should be before the configuration, or,
printing the error/warning is fine, as long as the man page also comes up.
And yes I realize that in my current state, the man page will give me lots of
good information, and then in a sense it will all be wrong since I can't use it
(tree falling in a far away forest).
I'll fix my setup of course, by setting package_msdev or whatnot to
/c/msdev/80, but I think perhaps the man behavior should be better.
Perhaps.
(I setup to \msdev\80, then clean reinstalled Windows; the compiler works fine,
but there's no registry entries.)
- Jay
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
