> > chmod 755 compile
> > ./compile tcpclient.c
> > ./compile: cc: not found
> > *** Error code 1
> Bad example.
not a bad example. get a standard solaris machine (without
paying for sun's sunpro cc) and install gcc.
try to compile anything of dans for the first time
(ie; first time compile, not new software
for the first time). I work with admins who just
can't figure out his compiling mechanism.
> If you do not have a functioning C compiler installed on your system, you
> have no business compiling or installing any software, not just Qmail.
I have never said that I do not have a functioning C compiler.
You have said and assumed this. You have assumed incorrectly.
> > and see that games being played with conf-cc ...
> > but then ld will fail, and I'll have to do the same for that after
> > the make fails.
> > Why not mention *this* in this INSTALL?
> Why make so much fuss about this?
Why? because it's necessary in order to compile?
> This is a minor glitch. Although it's real cause is your broken C
> compiler, let's say that's even not case. Things like this happen all the
> time, and I don't see the big deal about it.
I do not have a broken C compiler. You can say it as much and as
often as you like, but that doesn't make it any more true.
> The only item I'll agree with you on is that djb should be using GNU
> auto-bloat, in order to handle convoluted compilers like that.
./Configure is nice... but it's not the only way. Dan's way works --
once you've dug through the source. Gee, one line in the install/readme
would prevent this.
Why does one have to read the qmail FAQ just to be able to
install qmail Can you answer that?
Scott
