On Thu, Sep 11, 2008 at 02:01:35AM -0400, Christopher Faylor wrote: >On Wed, Sep 10, 2008 at 10:38:27PM -0700, Brian Dessent wrote: >>Christopher Faylor wrote: >>>I haven't tried this with the actual released compiler yet but, >>>assuming it works the same way, mm I wrong or is there something wrong >>>with this compiler? The code it creates seems to be correct (and >>>Cygwin is noticeably smaller) but I'd like to get rid of all of the new >>>warnings. I can't get rid of this one because I don't see how to do >>>that. >> >>The warning is correct, technically. When compiling strsig.cc, you >>want the variable to be exported, not imported. When compiling >>everything else that includes signal.h, you want it to be imported. >> >>There are actually two things wrong here, as I see it: one, dllexport >>should not be necessary at all as the exports are controlled by the >>.def file. > >sys_sigabbrev is not in cygwin.def. There are several variables which >are not exported via cygwin.def.
Actually make that "there were several variables". Somewhere along the line most of the variables migrated into cygwin.din which makes the dllexport redundant. cgf -- 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/
