On Mar 21 16:03, Peter Foley wrote: > On Mon, Mar 21, 2016 at 3:55 PM, Corinna Vinschen > wrote: > > But using -std= when building Cygwin wouldn't change the fact that we > > might need this delete anyway for applications built with -std=c++14 > > or do I miss something? > > This patch is specifically for building cygwin1.dll > I haven't tested building programs with -std=c++14, but that should > not be affected at all by this patch. > I believe the only reason this issue occurs at all is that cygwin1.dll > explicitly does not link with libstdc++. I applied the original patch and added a diagnostic pragma to disable the warning for now. We definitely have keep in mind that we might have to export this function at one point for C++14 applications playing dirty tricks. I seriously wonder if we shoudn't do this proactively. Again, see https://cygwin.com/ml/cygwin-patches/2009-q3/msg00010.html for the reasdon to export the functions at all. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat