Selon Giles Robertson <[EMAIL PROTECTED]>: > > please see the following link for the errors... > > > http://mail.flightgear.org/pipermail/flightgear-users/attachments/200506 > 09/2ff42b56/SimGear_2.gif > > It's much easier for us to attempt diagnose if we can see the full error > log. If you type: > > make > log.txt > > at the Cygwin command prompt, and then copy the last section of that > file (log.txt) into your email (from the last line beginning "gcc" > downwards), we can see how the compiler is being called, and where the > errors start. (Once a compiler hits an error, further errors may be a > knock-on from it not functioning properly previously, so it's often the > first error which is most relevant to solving the problem)
Try to include the error stream also : make > log.txt 2>&1 -Fred _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
