Bug#951151: polymake: test failure on mips64el

2020-02-19 Thread Benjamin Lorenz
On 13/02/2020 16.53, Benjamin Lorenz wrote: > On 13/02/2020 13.18, David Bremner wrote: >> Benjamin Lorenz writes: It looks like it's flint related? >>> >>> Yes, I think this is a bug in flint and for now I suggest disabling the >>> flint-interface of polymake with the configure option --with

Bug#951151: polymake: test failure on mips64el

2020-02-13 Thread Benjamin Lorenz
On 13/02/2020 13.18, David Bremner wrote: > Benjamin Lorenz writes: > >> >>> It looks like it's flint related? >> >> Yes, I think this is a bug in flint and for now I suggest disabling the >> flint-interface of polymake with the configure option --without-flint on >> mips64el. This has basically

Bug#951151: polymake: test failure on mips64el

2020-02-13 Thread David Bremner
Benjamin Lorenz writes: > >> It looks like it's flint related? > > Yes, I think this is a bug in flint and for now I suggest disabling the > flint-interface of polymake with the configure option --without-flint on > mips64el. This has basically no functionality loss as polymake will use > its own

Bug#951151: polymake: test failure on mips64el

2020-02-12 Thread Benjamin Lorenz
After some time of setting this up and building I can reproduce it and got a better backtrace which seems well inside flint (up to frame 6): Program received signal SIGSEGV, Segmentation fault. 0x0040014cb29c in flint_mpz_set_ui (r=0x400c8e3dd0, r=0x400c8e3dd0, u=9223372036854775837) at ./

Bug#951151: polymake: test failure on mips64el

2020-02-11 Thread David Bremner
Package: polymake Version: 4.0-2 Severity: serious Justification: FTBFS After building on mips64el, I get HOME=$(mktemp -p build -d) perl perl/polymake --script run_testcases --emacs-style polymake: WARNING: created private directory build/tmp.8rZQYU191i/.polymake [snip] [ /core/functions/S