Once again, I've managed to fix my own problem, albeit a few hours
later... :-) I figured out that gcc was accidentally calling cpp from
Borland C++, instead of the one in the /bin directory. (Makes me wonder if
Borland C++ is actually working, I'm not the sole user of this machine, and
have never tried it!) Anyways, everything seems to be working just great
now!
|
