> Everything that you have to compile depends on the name of the C compiler.
> I edited conf-cc and conf-ld once when I was first building qmail, saved
> it as a local patch, and problem was forever solved. One gets very used
> to doing that on Solaris to get things to compile with gcc instead,
> particularly given that I *have* cc (/opt/SUNWspro/bin/cc, to be precise).
bingo. Lets say I had your setup. Fine, I type make and it uses "cc"
.. which, if it's sunpro, is better than gcc anyway, but *if* I wanted
to compile using gcc? How would I do that? I'd have to dig through the
source until I found the "tricks" ...
*I* kow the tricks. As someone else said, every since first struggling
with it when trying to compile qmail, I have known to look for
conf (in fact, I look for conf* and */conf*) just to look around.
> > You know, solaris boot has a check for the current user to be "root" so
> > if you put another entry in the /etc/passwd *before* root with uid 0, a
> > solaris system won't boot? Isn't that kind of pathetic? Why can't the
> > script check "id" or something for the uid instead of depending on the
> > *text* output of some user check?
> Don't create multiple UID 0 accounts. You'll horribly regret it later.
> Been there, done that.
Why do people say this? What the hell does it matter? People these days
spout a bunch of baseless crap. If you want to discuss this, I'd be
glad to take it to email to see where we differ in philosophies.
Scott
