On 23.09.2010, at 14:03, MacArthur, Ian (SELEX GALILEO, UK) wrote: >> At least here's a workaround: add -Wl,--enable-auto-import > > Hmm, I thought we have that set anyway? > > The makeinclude from my fltk-1.1 DLL build shows: > > DSOCOMMAND = $(CXX) $(DSOFLAGS) -shared -Wl,--whole-archive > -Wl,--export-all-symbols -Wl,--enable-runtime-pseudo-reloc > -Wl,--enable-auto-import -Wl,--enable-auto-image-base -o $@
That's for building the dll, isn't it? (see below) > And the fltk-config has: > > LDFLAGS="-mwindows -L/usr/local/lib -mno-cygwin -Wl,--enable-auto-import > -Wl,--enable-runtime-pseudo-reloc" fltk-config with which (configure) arguments? I don't see it in my build. > Though I don't have a DLL fltk-1.3 build here for comparison... It happens during the stock (non-shared) build, and that's what puzzles me. You get the warning when building fluid (IIRC) and fluid crashes with error (exit) code 0xC0000005 or so... I thought --enable-auto-import would be needed to build a dll, but now you need it also to build executables. Unless I'm missing something essential, but I think that I found something about it in the net. I'll have to dig this out again... Okay, here is one example: http://www.cygwin.com/ml/cygwin/2009-06/msg00215.html The reply ends in: "This is a known problem. The explanation is rather technical and long, IIRC. Just use -Wl,--enable-auto-import for all GCC 4.3 compiled code and you are fine." And see this one: 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." This message is somewhat old (Mar 2009), but maybe there hasn't been the "next" binutils release, or it hasn't been fixed, or we are using the wrong binutils tools? As I said, I didn't investigate it further, but I *believe* that I installed the newest binutils version I could find on the (sourceforge) MinGW download site. I think that Dave Korn is one of the gcc maintainers. >> Well, we *have* a patch, and I think that it is so far okay, but >> I'd like to have someone else check it. Ian, Greg, could you maybe >> take a look at it? > > I'll try, but this week is proving "difficult"... That would really be fine. <OT> > For svn versions, I have been using both the TortoiseSVN client (which > is fine, and has a GUI) and the slik svn tools for the command line > stuff. > > To be honest, I mainly use the slik svn tools as a lot of it I do via > scripts anyway... This works fine from within the Msys shell *most of > the time*. Sometimes, but only very occasionally, I find I have to run > it from a DOS box, if I am doing interactive stuff, as there seems to be > some incompatibility between the slik svn i/o and the Msys shell... Thanks, I would only need it for commandline usage, and currently I can use the Cygwin svn from the MinGW shell (mintty with bash, BTW), but when I want to get rid of Cygwin entirely... </OT> Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
