Hi Jay,
Thanks for bringing this up. I mainly work on the native-ish Windows
targets (MinGW), so I'm not really a Cygwin guy, but see below.
Jay wrote:
I'm still testing this but it does seem to be two smoking guns.
The first one shot a blank but I doubt I'll find a third. :)
...
> Can someone vet and apply these changes? Thanks.
If you figure out a definitive fix, please submit it to gcc-patches@ in
the proper format. See <http://gcc.gnu.org/contribute.html> for the
instructions on specifically how to submit a patch.
You will need to update your patch to SVN trunk or a recent 4.4
snapshot, since that is what it would be applied to.
Nobody builds gcc + cygwin in an integrated tree?
I wish I could integrate more into The One Tree.
I so dislike everything being separate..
Probably not, especially because relatively few people are doing their
own Cygwin builds at all.
Similarly, this is kind of yucky but I guess ok:
...
Or declare them __declspec(dllimport) on Cygwin (or whatever is the gcc equiv).
I think libiberty it should do this conditional on Cygwin. If that
seems to fix it, you should submit a patch. The ideal is to avoid using
auto-import entirely if possible.
