| | | 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 (...) (28 years ago, 17-Jun-96, to lugnet.robotics.handyboard)
|
