Test issues when building on mipsel architecture

[tillea]

Hello,

there is a bug in the Debian bug tracking system concerning building libminc on mipsel architecture. It is about two failed tests out of (49 tests are passing). When looking at the output it looks like a typical integer overflow:

       Start  1: ezminc_rw_test
  1/51 Test  #1: ezminc_rw_test ...................   Passed    0.23 sec
       Start  2: minc_types-1
  2/51 Test  #2: minc_types-1 .....................***Failed    0.15 sec
  364c364
 <    image[1] = 255
 ---
 >    image[1] = 0
 373c373
 <    image[1] = 127
 ---
 >    image[1] = -128
 382c382
 <    image[1] = 65535
 ---
 >    image[1] = 0
 391c391
 <    image[1] = 32767
 ---
 >    image[1] = -32768
 400c400
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = 0
 409c409
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 418c418
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 427c427
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 481c481
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 553c553
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09

      Start  3: minc_types-2
 3/51 Test  #3: minc_types-2 .....................***Failed    0.93 sec
 364c364
 <    image[1] = 255
 ---
 >    image[1] = 0
 373c373
 <    image[1] = 127
 ---
 >    image[1] = -128
 382c382
 <    image[1] = 65535
 ---
 >    image[1] = 0
 391c391
 <    image[1] = 32767
 ---
 >    image[1] = -32768
 400c400
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = 0
 409c409
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 418c418
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 427c427
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 481c481
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09
 553c553
 <    image[1] = 2.14748e+09
 ---
 >    image[1] = -2.14748e+09

      Start  4: icv_dim1-1

Here you can find the full build log (the issue can be found at the end):
https://buildd.debian.org/status/fetch.php?pkg=libminc&arch=mipsel&ver=2.3.00-2&stamp=1448468687

The according bug in the Debian BTS is
https://bugs.debian.org/806243

Any help to fix this would be welcome.

Kind regards

   Andreas.

[rdvincent]

Thanks for the report.

[tillea]

There is another report that the build problem occures only on certain mips boards. Please look here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806243#17

[rdvincent]

I do not have access to any physical MIPS hardware, and the emulated system I use does not exhibit the problem. I am trying to build an emulated system using a more recent version of the OS to see if that has an impact, Is there any way I can get remote access to a physical system of the right kind? Or, failing that, does anyone have an emulated system that exhibits the problem?

[tillea]

Hi,

I'm just forwarding this mail from upstream. From my perspective it is
possibly not a bug in libminc but rather a problem of certain mips
hardware. I wonder in how far this is a serious bug of libminc and
should be downgraded to important (at maximum).

Kind regards

   Andreas.

On Sat, Dec 05, 2015 at 09:01:29AM -0800, Robert D Vincent wrote:

I do not have access to any physical MIPS hardware, and the emulated system I use does not exhibit the problem. I am trying to build an emulated system using a more recent version of the OS to see if that has an impact, Is there any way I can get remote access to a physical system of the right kind? Or, failing that, does anyone have an emulated system that exhibits the problem?

---

Reply to this email directly or view it on GitHub:
#66 (comment)

http://fam-tille.de

[tillea]

On Sat, 2015-12-05 at 18:21 +0100, Andreas Tille wrote:

Hi,

I'm just forwarding this mail from upstream.  From my perspective it is
possibly not a bug in libminc but rather a problem of certain mips
hardware. 

I haven't looked at this build failure in particular, but I do know the
FPUs on the Loongson machines are a little suspect (giving almost
correct answers to most things) so I would not be surprised if this
was a hardware problem.

I wonder in how far this is a serious bug of libminc and should be
downgraded to important (at maximum).

Since libminc has never successfully built on mipsel, this bug
shouldn't have been serious in the first place (regardless of what was
causing it).

James