Dave Korn wrote: > That I can't say. But assuming the build uses proper dependencies in the > makefile, you should be able to workaround it by cutting and pasting that line > into your shell, replacing 'gcc' by 'g++' as you go, and once you've got past > that manually the rest of the build should run to completion.
Normally that might work but in this case it misses the point, as the whole purpose of this perl module is to dynamically invoke the C++ compiler at runtime to compile the inline C++ bits in the script. And if it's invoking the compiler wrong it makes this essentially useless as all the stuff it feeds the compiler is dynamically generated. But I agree that this is a bug somewhere in the module, and is not related to Cygwin or gcc. Looking at its sources it seems to have the proper logic to use g++ for linking and/or adding -lstdc++ so I would suggest you need to contact the module's author. 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/
