Yes of course you're right, I don't have gcc 4.5.1, I have gcc 4.3.4. I incorrectly assumed that I had 4.5.1 because I installed gcc only this past month.
On Feb 10, 3:24 pm, Jason <ja...@njkfrudils.plus.com> wrote: > On Thursday 10 February 2011 18:56:58 jason wrote: > > > Hi > > > I just updated my cygwin on Vista 64 to the latest and now its back > > working again(it continued to work on Vista32, weird!) > > gcc-3.4.4 works OK and so does gcc-4.3.4 , yet to try 4.5.1 , as it > > cant find the c++ compiler for some reason. > > It's because the Cygwin setup doesn't choose the correct libstdc++ , of course > every time you update it uninstalls 4.5 and reinstalls 4.3.4 as that is the > default.Clearly they think 4.5 is not ready for prime time , we basically work > on it , but as it's such a hassle to keep 4.5 on your system I'm not going to > do any testing on it.They let you keep 3.4.4 and 4.3.4 on the system but not > 4.5 > > Jason > > > Jason > > > On Feb 10, 4:55 pm, CTSmith <smit...@gmail.com> wrote: > > > In the options, I reduced my previous configure from > > > ./configure --enable-gmpcompat --enable-cxx=detect --enable-assert > > > to > > > ./configure --enable-gmpcompat --enable-cxx=detect. > > > > This was successful. It seems that the only bug is in assertion > > > checking. > > > Jason, I am indeed using gcc 4.5. Hopefully this is actually good > > > news. > > > Thank you for your support, MPIR community is first class. > > > > Chris > > > > On Feb 10, 3:00 am, Jason <ja...@njkfrudils.plus.com> wrote: > > > > Hi > > > > > My guess is that your using gcc-4 series , I've only tested it on the > > > > gcc-3.4 series on Cygwin. We have had a lot of problem with Cygwin > > > > recently , in the summer I couldn't even download the 4 series gcc. > > > > Then in about november it started to fail to compile MPIR completely , > > > > this were versions that have always worked before. They seem to of > > > > fixed that now , but I did not try the 4 series compiler.In the > > > > configure options try adding > > > > ./configure CCX=-Wno-deprecated > > > > to see if that overcomes your problem , the other alternate is to > > > > replace the offending line where we include the depreciated header > > > > file , that may break something else , my knowledge of C++ is minimal. > > > > I'll try an have a look at it this weekend. > > > > > Jason > > > > > On Thursday 10 February 2011 10:07:33 Bill Hart wrote: > > > > > Unfortunately I don't know what is causing this. Jason Moxham did > > > > > most of the recent work on Cygwin and did lots of testing. It should > > > > > be fine. I can only recommend ensuring you have the latest Cygwin. > > > > > If there is still a problem, maybe try adding a #include <string> as > > > > > you suggest and see if the problem goes away. This problem is > > > > > certainly confined to certain versions of Cygwin it seems. > > > > > > Bill. > > > > > > On 9 February 2011 19:06, CTSmith <smit...@gmail.com> wrote: > > > > > > As posted in a previous discussion by the author, this is for Intel > > > > > > Core i3 with Windows 7. > > > > > > > Make check progresses to "Making check in cxx", then gives a > > > > > > warning followed by an error. > > > > > > > The output looks like this: > > > > > > ... > > > > > > Making check in cxx > > > > > > make[3]: Entering directory '/cygdrive/c/mpir/mpir-2.2.1/tests/cxx' > > > > > > make t-assign.exe t-binary.exe t-cast.exe t-constr.exe > > > > > > t-headers.exe t-istream.exe t-locale.exe t-misc.exe t-ops.exe > > > > > > t-ostream.exe t- prec.exe t-rand.exe t-ternary.exe t-unary.exe > > > > > > make[4]: Entering directory '/cygdrive/c/mpir/mpir-2.2.1/tests/cxx' > > > > > > g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../tests -m32 -O2 - > > > > > > fomit-frame-pointer -mtune=core2 -march=core2 -c -o t-assign.o t- > > > > > > assign.cc > > > > > > In file included from > > > > > > /usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++/ > > > > > > backward/strstream:51, > > > > > > from ../../tests/tests.h:469, > > > > > > from t-assign.cc:30: > > > > > > /usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++/backward/ > > > > > > backward_warning.h:33:2: > > > > > > warning: #warning This file includes at least one deprecated or > > > > > > antiquated header which may be removed without further notice at a > > > > > > future date. Please use a non-deprecated interface with equivalent > > > > > > functionality instead. For a listing of replacement headers and > > > > > > interfaces, consult the file backward_warning.h. To disable this > > > > > > warning use -Wno-deprecated. > > > > > > In file included from t-assign.cc:30: > > > > > > ../../tests/tests.h:473: error: 'string' does not name a type > > > > > > make[4]: *** [t-assign.o] Error 1 > > > > > > make[4]: Leaving directory 'cygdrive/c/mpir/mpir-2.2.1/tests/cxx' > > > > > > ... > > > > > > make: *** [check] Error 2 > > > > > > > There is much discussion in C++ forums about using std::string, but > > > > > > I'm not sure if it applies here. > > > > > > Thank you in advance, > > > > > > Chris > > > > > > > -- > > > > > > 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 > > > > > > athttp://groups.google.com/group/mpir-devel?hl=en.-Hide quoted > > > > > > text - > > > > - Show quoted text - -- 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.
