Alright, now the make check makes it down to .../tests/cxx, and fails
there.
Here is the part of the message that applies:
...
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-tern
ary.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-p
ointer -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/str
stream: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 heade
r 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 re
placement headers and interfaces, consult the file backward_warning.h.
To disabl
e 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
Might this have something to do with the version of cygwin and not
mpir?
Thanks in advance,
Chris
On Feb 8, 3:43 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
> A pure guess, Windows is running out of memory when running the test.
> I might be wrong, however, I think it writes some really large strings
> when it does the tests. Cygwin might not like that.
>
> Bill.
>
> On 8 February 2011 19:32, CTSmith <smit...@gmail.com> wrote:
>
> > Bill,
>
> > Thanks for your response!
> > You know, it's funny, but I'd run it twice when i posted the thread. I
> > decided, 'what the heck, 3rd time's the charm' and ran it a third
> > time. This time it passed. Perhaps there was interference of some
> > sort, but I can't make sense of it... anyways, I'll still give all
> > details around the problem in the event that my build turns out buggy.
> > My apologies.
>
> > I'm using a Toshiba Portege R705 with Intel Core i3, running Windows 7
> > Home Premium.
> > I'm using Cygwin Bash Shell.
>
> > My code in:
> > ./configure --enable-gmpcompat --enable-cxx=detect --enable-assert
>
> > For brevity, I'll only include the messages that seem to be pertinent:
>
> > ...
> > PASS: convert.exe
> > PASS: io.exe
> > /bin/sh: line 1: 6196 Aborted (core dumped) "$tst" > t-
> > inp_str
> > .log-t 2>&1
> > FAIL: t-inp_str.exe
> > PASS: logic.exe
> > PASS: bit.exe
> > ...
> > ...
> > ==================================================
> > 1 of 59 tests failed
> > See tests/mpz/test-suite.log
> > $
> > ==================================================
> > make[5]: *** [test-suite.log] Error 1
> > make[5]: Leaving directory '/cygdrive/c/mpir/mpir-2.2.1/tests/mpz'
> > ...
> > make: *** [check] Error 2
>
> > Now the log file:
> > ==========================================
> > MPIR 2.2.1: tests/mpz/test-suite.log
> > ==========================================
>
> > 1 of 59 tests failed.
>
> > .. contents:: :depth: 2
>
> > FAIL: t-inp_str.exe (exit: 134)
> > ===============================
>
> > t-inp_str.c:97: GNU MP assertion failed: fp != ((void *)0)
>
> > Once again, thanks for the response and I'm glad that it seems to be
> > working and hopefully I didn't waste your time on this one.
>
> > On Feb 8, 9:42 am, Bill Hart <goodwillh...@googlemail.com> wrote:
> >> Can I ask, what is the machine and operating system, and what message
> >> did it give upon failure?
>
> >> We don't expect any failures except in the known cases listed on the
> >> web page. If you find another failure it is likely a bug which we
> >> would like to know more about.
>
> >> Bill.
>
> >> On 8 February 2011 16:02, CTSmith <smit...@gmail.com> wrote:
>
> >> > During make check, only 1 test fails: t-inp_str.exe. Is mpir ok still?
>
> >> > --
> >> > 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.
>
> > --
> > 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.
--
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.
