Angelo Graziosi wrote: > It tries to build C++ with gcc: > > gcc bytes_to_int_flag_generator.o -o bytes_to_int_flag_generator > > ... > So the question is : what could be the cause of this different behaviour ? >
I've seen this a million times. It's a makefile that doesn't know about $EXEEXT and assumes that executables have no extension. Because of this one of the stock built-in make rules gets invoked instead of the proper link command. Look in the Makefile for the rule that generates the final binary and I'm willing to bet that it has no $EXEEXT. This works fine on linux because there is no extension for executables there. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
