> I've had tcpserver compile just fine even with HP's broken compiler. It > seems as if you're trying to find fault just to try and prove your point. > If you know/knew in advance of your non-standard compiler setup you'd be > prepared for it. *sigh* You just don't get it... do you. I have a standard compiler set up. I have gcc. I do not have cc. I get 99% of my programs in source and they tell me to edit the Make file and change the "cc" line to "gcc" or to type ./Configure. Both of these get me to compile (maybe I have to define solaris, etc.) just fine. Then comes qmail, et al., does it use Makefile with CC=gcc? no. Does it use ./Configure? no. It says "type make; make config check; # that's all!" BUT IT IS NOT ALL. That's all (I'm trying to say). Scott
- RE: documentation, documentation, documentation Vince Vielhaber
- RE: documentation, documentation, documentati... Scott D. Yelich
- Re: documentation, documentation, documentation Adam D. McKenna
- Re: documentation, documentation, documentati... Scott D. Yelich
- Re: documentation, documentation, documen... Harald Hanche-Olsen
- Re: failure notice (fwd) Vince Vielhaber
- poor documentation example Scott D. Yelich
- Re: poor documentation example Racer X
- Re: poor documentation example Scott D. Yelich
- Re: poor documentation example Vince Vielhaber
- Re: poor documentation example Scott D. Yelich
- Re: poor documentation example James Smallacombe
- Re: poor documentation example Mark Delany
- Re: poor documentation example Russ Allbery
- Re: poor documentation example Mark Delany
- Re: poor documentation example Russ Allbery
- Re: poor documentation example Racer X
- Re: poor documentation example mgibbins
- Re: poor documentation example Russ Allbery
- Re: poor documentation example Julian L.C. Brown
- Re: poor documentation example Jay Soffian
