Bug#874220: openni2 mustn't build with NEON on armel/armhf

2017-09-11 Thread Adrian Bunk
On Fri, Sep 08, 2017 at 07:17:59PM +0200, JOSE LUIS BLANCO CLARACO wrote: > Hi Adrian, > > Thanks for tagging "mrpt" here! > Is there any expected action on our side? Should we disable linking > against openni2 in armhf in the meanwhile... or it's better to wait > for this bug to be solved? It

Bug#874220: openni2 mustn't build with NEON on armel/armhf

2017-09-08 Thread JOSE LUIS BLANCO CLARACO
Hi Adrian, Thanks for tagging "mrpt" here! Is there any expected action on our side? Should we disable linking against openni2 in armhf in the meanwhile... or it's better to wait for this bug to be solved? It actually blocks mrpt to get into testing... Cheers, On Mon, Sep 4, 2017 at 12:45 PM,

Bug#874220: openni2 mustn't build with NEON on armel/armhf

2017-09-04 Thread Adrian Bunk
Source: openni2 Version: 2.2.0.33+dfsg-7 Severity: serious Tags: patch Control: affects -1 src:mrpt NEON is not part of the armel and armhf architecture baselines, it is therefore not permitted to use NEON unless proper runtime detection is used. NEON is also not available on the autobuilders.