Bug#806243: [libminc] Test issues when building on mipsel architecture (#66)
Control: severity -1 important On Sat, 16 Jan 2016 13:17:15 +0100 Andreas Beckmann wrote: > On Sat, 05 Dec 2015 20:56:01 + James Cowgill > wrote: > > 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). > > But the minc package (before the split) has built successfully on > mipsel, so this FTBFS is blocking the transition, since minc-tools is > missing a current build on mipsel. The old minc package has been decrufted, so the missing mips*el builds shouldn't be blocking any longer. Andreas
Bug#806243: [libminc] Test issues when building on mipsel architecture (#66)
Control: block 800414 with -1 . On Sat, 05 Dec 2015 20:56:01 + James Cowgill wrote: > 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). But the minc package (before the split) has built successfully on mipsel, so this FTBFS is blocking the transition, since minc-tools is missing a current build on mipsel. Andreas
Bug#806243: [libminc] Test issues when building on mipsel architecture (#66)
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 signature.asc Description: This is a digitally signed message part
Bug#806243: [libminc] Test issues when building on mipsel architecture (#66)
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: > https://github.com/BIC-MNI/libminc/issues/66#issuecomment-162223456 -- http://fam-tille.de
