On 23.09.2010, at 18:32, Ian MacArthur wrote: >> http://www.cygwin.com/ml/cygwin/2009-03/msg00663.html >> >> "It has started to happen now because libstdc++ is a DLL for the >> first time. We've fixed upstream ld to enable the feature by default >> and these warnings will disappear in the next binutils release." > > OK, I see. Yup, that'll do it, so we need to enable auto-import even for > *static* builds with gcc 4.3 or later, then. Bother. > > And that may be a pain if libstdc++ now needs to be loaded as a DLL, as > that will reduce the portability of my static builds substantially - now > I need to distribute the exe *and* a DLL, assuming most folk will not > have the mingw-libstdc++ DLL installed by default. > Double bother...
Oh, yes! If we get that dependency and can't avoid to link against the dll, then ... that would be really bad. But there may be hope. I don't think that I got the linker warnings for all programs in the *test* directory. That might mean that there are some that have the dependency and some that don't. (?) I don't have my MinGW installation here available, but I'll try to make a fresh installation on my home PC to do more tests (my office installation is a manually updated older installation, and I may have missed something...). However, this won't happen before next week :-( Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
