From: Kevin.Low > [...] I think knowing gcc 3.2 is not the culprit will help.
It probably would, but we don't know that. GCC 3.2 seems to date back to around August 2002, and there were also 3.2.1, 3.2.2, and 3.2.3 over the next several months, so it's certainly pretty old, and it was probably not entirely defect-free. With a transcript showing what happened, someone might be able to assign blame (always the first and most important step in problem resolution). After that, many things are possible. ------------------------------------------------------------------------ Steven M. Schweda [EMAIL PROTECTED] 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547
