On Thu, Apr 9, 2009 at 4:14 AM, Bill Hart <[email protected]> wrote:
> I'm going to downgrade the bug we have listed in trac for cygwin32 > from a blocker, as it only appears to affect old versions of Cygwin. > I'm not totally sure we can do anything for such setups. The cygwin I have that is experiencing this problem is on my newest machine that I built in September 2008. I installed cygwin on November 13, 2008 so how old do you consider "old" to be? By default cygwin still installs gcc v3 and you can also tell it to install gcc v4 along-side. Am I seeing this because I'm using the default gcc v3 an if I used gcc v4 the problem would go away? Or how did you set up your "new" cygwin so it works? Jeff. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
