Also no issues with 0.9. So I've drawn a blank on this one. Bill.
2009/4/10 Bill Hart <goodwillh...@googlemail.com>: > Hi Jeff. I didn't manage to reproduce the Cygwin32 issue with > mpir-1.0, even with a core 2 build, yet. I'm going to try 0.9 now to > see if an earlier version of 1.0 might have had the bug (which would > presumably be present in 0.9). > > Is there any chance you could check out trunk from svn: > > http://modular.math.jmu.edu/svn/mpir/mpir/trunk > > and see if the issue still persists for you. > > Also, could you go into the top level of the source tree and type > > config.guess > > and tell us what it returns. > > Finally, we'd like to know what > > ln -v > > returns, to see if this is the libtool issue that was reported ages > ago on the GMP list. I don't think it can be that, as modern Cygwins > don't suffer from it, but we'll check to make sure. > > Thanks. > > Bill. > > 2009/4/9 Jeff Gilchrist <jeff.gilchr...@gmail.com>: >> >> On Thu, Apr 9, 2009 at 7:13 AM, Bill Hart <goodwillh...@googlemail.com> >> wrote: >> >>> That's interesting. My Cygwin uses (gcc -v): >>> >>> gcc version 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) >>> >>> It looks like it was installed November 2007, so about 18 months old. >>> I've not done anything special to it, such as installing gcc version >>> 4. >> >> Looks like you have the "old" version, maybe it is an issue on "new" >> versions of cygwin. >> >>> Do I recall correctly that you have a Core 2, Jeff? >> >> That is right, a Q9550 (the 45nm Core2 with SSE4 instructions) >> >>> Can we also compare assembler versions (as -v). I have: >>> >>> GNU assembler version 2.17.50 (i686-pc-cygwin) using BFD version >>> 2.17.50 20060817 >> >> $ gcc -v >> Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs >> Configured with: >> /usr/build/package/orig/test.respin/gcc-3.4.4-3/configure --verbose >> --prefix=/usr - >> -exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib >> --libexecdir=/usr/lib --mandir=/usr/share/man >> --infodir=/usr/share/info >> --enable-languages=c,ada,c++,d,f77,pascal,java,objc --enable-nls >> --without >> -included-gettext --enable-version-specific-runtime-libs --without-x >> --enable-libgcj --disable-java- >> awt --with-system-zlib --enable-interpreter --disable-libgcj-debug >> --enable-threads=posix --enable-j >> ava-gc=boehm --disable-win32-registry --enable-sjlj-exceptions >> --enable-hash-synchronization --enabl >> e-libstdcxx-debug >> Thread model: posix >> gcc version 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) >> >> $ as -v >> GNU assembler version 2.18.50 (i686-pc-cygwin) using BFD version (GNU >> Binutils) 2.18.50.20080625 >> >> So we have the same gcc but I have a newer assembler than you. >> >> Jeff. >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
