That's cygwin 1.5. The gcc4 package is a standard one on the list when running "setup", so any user of cygwin might have installed it, and it might be worthwhile taking its possible presence into account, to save the user some debugging time.
On Oct 22, 11:37 am, Jason Moxham <ja...@njkfrudils.plus.com> wrote: > On Thursday 22 October 2009 15:42:05 Dan Grayson wrote:> To get mpir to pass > its C++ tests under cygwin (if I configure with -- > > enable-cxx) I had to also add -Wl,--enable-auto-import to LDFLAGS. > > The warning message from ld if you don't have that option specified > > doesn't sound very scary, because it says it's doing the auto import, > > anyway, without being asked. And some of the failing programs linked > > with no warnings. But something goes very wrong, and the program > > (e.g., t-assign.exe) can't even start up (at least under gdb), > > returning an error code of 5. That was with gcc 4.3.2. > > Is this with cygwin 1.5 ? or the new cygwin 1.7? > Have you tried gcc 3.4.? on cygwin ? > > If this is with the new cygwin 1.7 , I can install it and give it a go , I > assume you can install both old and new cygwin side by side ? > > mpir is known to pass c++ tests etc on default cygwin install , ie cygwin 1.5 > with gcc-3.4.? > > Thanks > Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
