Hamish McIntyre-Bhatty via Cygwin writes: > I've run into a blocker when trying to build wxPython that wasn't a > problem when I last did it (which amittedly was over a year ago). Some > -werror flags are being passed to GCC, but I can't see where they're > coming from. Are there any defaults set for GCC that mean -werror > might be turned on?
No, that comes from the package. But a newer gcc might have more warnings that now turn into an error. > When I build wxPython on my host (Linux) system, I don't get the same > issues, so I'm assuming there are defaults being set somewhere. If > anyone could offer some help I'd be very appreciative. Pass 'Wno-error=…' into CCFLAGS or something like that or if it's just a handful of locations bracket them with #pragma push #pragma GCC diagnostic ignored "-W…" /* offending code */ #pragma pop Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
