On Tue, Feb 18, 2014 at 2:50 PM, David Daney wrote:
> On 02/17/2014 01:28 PM, Andreas Barth wrote:
>>
>> * Felipe Sateler (fsate...@gmail.com) [140217 20:33]:
>>>
>>> The package liblo runs a test suite at build time. This test suite
>>> failed in mipsel (but not mips)[1]. I tried to reproduce the
On 02/17/2014 01:28 PM, Andreas Barth wrote:
* Felipe Sateler (fsate...@gmail.com) [140217 20:33]:
The package liblo runs a test suite at build time. This test suite
failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
eder.d.o but it passed.
Liblo does use unaligned access (li
On Mon, Feb 17, 2014 at 6:28 PM, Andreas Barth wrote:
> * Felipe Sateler (fsate...@gmail.com) [140217 20:33]:
>> The package liblo runs a test suite at build time. This test suite
>> failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
>> eder.d.o but it passed.
>>
>> Liblo does u
* Felipe Sateler (fsate...@gmail.com) [140217 20:33]:
> The package liblo runs a test suite at build time. This test suite
> failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
> eder.d.o but it passed.
>
> Liblo does use unaligned access (liblo had to be removed from sparc
> for
The package liblo runs a test suite at build time. This test suite
failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
eder.d.o but it passed.
Liblo does use unaligned access (liblo had to be removed from sparc
for this reason).
But I'm confused as to why does the buildd error ou