Re: `make check` error

105 views
Skip to first unread message

Alessandro Andrioni

unread,
May 14, 2013, 8:11:01 AM5/14/13
to mpir-...@googlegroups.com
It seems to be the exact same error from https://groups.google.com/forum/?hl=en&fromgroups=#!topic/mpir-devel/oLk3gMULxu0 Any plans for patching it in the git repository? I'm writing a PKBGUILD (so it's easy to install and manage in Arch Linux) for the git version of mpir, so I can it patch there too in case this doesn't get changed.

On Tuesday, May 14, 2013 8:57:58 AM UTC-3, Alessandro Andrioni wrote:
Hello, 

I had the following error when running `make check` after compiling mpir from the Github repository (https://github.com/wbhart/mpir).

If it helps, it seems it is using the following CFLAGS: -std=gnu99 -m64 -fomit-frame-pointer -O2 -march=corei7-avx -mtune=corei7-avx

$ make check
(...)
PASS: t-root
/bin/sh: line 1: 27163 Segmentation fault      (core dumped) "$tst" > t-scan.log-t 2>&1
FAIL: t-scan
PASS: t-set_d
PASS: t-set_f
PASS: t-set_si
PASS: t-set_str
PASS: t-set_sx
PASS: t-set_ux
PASS: t-sizeinbase
PASS: t-sqrtrem
PASS: t-tdiv
PASS: t-tdiv_ui
PASS: t-trial_division
PASS: st_hamdist
PASS: st_popcount
=============================================================
1 of 66 tests failed
See tests/mpz/test-suite.log
=============================================================
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory `/home/ra101324/workspace/mpir/tests/mpz'
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory `/home/ra101324/workspace/mpir/tests/mpz'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/ra101324/workspace/mpir/tests/mpz'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/ra101324/workspace/mpir/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/ra101324/workspace/mpir'
make: *** [check] Error 2

ra101324 at conway in ~/workspace/mpir (master●●)
$ cat tests/mpz/test-suite.log
==========================================
   MPIR 2.6.0: tests/mpz/test-suite.log   
==========================================

1 of 66 tests failed.  

.. contents:: :depth: 2


FAIL: t-scan (exit: 139)
========================

Bill Hart

unread,
May 14, 2013, 7:59:27 AM5/14/13
to mpir-devel
Usually caused by gcc 4.3.2 which is buggy.


--
You received this message because you are subscribed to the Google Groups "mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+...@googlegroups.com.
To post to this group, send email to mpir-...@googlegroups.com.
Visit this group at http://groups.google.com/group/mpir-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Bill Hart

unread,
May 14, 2013, 8:38:47 AM5/14/13
to mpir-devel
Oh I'm sorry, I misread that as a failure in t-root. Yes, you are right it is the same bug as Dan reported. 

It will be patched in the next release.

Bill.


--

Alessandro "Jake" Andrioni

unread,
May 14, 2013, 9:01:05 AM5/14/13
to mpir-...@googlegroups.com
Ok, thanks, then I'm going to patch it myself for now.

Is there a way to use a system yasm? The yasm binaries and headers
conflict with the system ones right now.

Bill Hart

unread,
May 14, 2013, 11:41:05 AM5/14/13
to mpir-devel
I don't think we have an option to use the system yasm at present.

Bill.

Alessandro "Jake" Andrioni

unread,
May 14, 2013, 10:00:43 PM5/14/13
to mpir-...@googlegroups.com
Curiously, the stable 2.6.0 version doesn't try to install yasm
binaries and headers, but the master from Github does try. Is this
intentional?

Bill Hart

unread,
May 15, 2013, 5:28:10 AM5/15/13
to mpir-devel
It might be. We have a script which runs in release versions only which fixes a few problems. But I don't know the answer to your question for sure.

Bill.
Reply all
Reply to author
Forward
0 new messages