Ubuntu
libwebp package

libwebp ftbfs on armhf

Bug #1630349 reported by Nish Aravamudan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libwebp (Ubuntu)
Fix Released
High
Nish Aravamudan
Revision history for this message
Nish Aravamudan (nacc) wrote :

I found a reference to a similar issue in openal-soft_1:1.16.0-3 from earlier this year.

http://gcc.1065356.n8.nabble.com/distro-test-rebuild-using-GCC-6-td1224722.html#a1226791

It seems the arm headers have changed how configure should detect neon support, and now the build is falsely detecting neon support, even though it's not passing the required -mfpu=neon flag. Given that neon support was not enabled before, I believe the best choice is to disable it via a configure flag.

Changed in libwebp (Ubuntu):
status: New → In Progress
assignee: nobody → Nish Aravamudan (nacc)
Revision history for this message
Nish Aravamudan (nacc) wrote :

It would appear, though, that libwebp has neon support, it just needs to be modified (configure script) to detect it properly, rather than relying on the header's existence. The code has runtime neon detection, so it should be safe to compile-in, if hte compiler supports the optoin.

Changed in libwebp (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libwebp - 0.5.1-2ubuntu1

---------------
libwebp (0.5.1-2ubuntu1) yakkety; urgency=medium

  * debian/patches/armhf_update_neon_support.patch: configure: do not
    rely on arm_neon.h for neon detection. Closes LP: #1630349.

 -- Nishanth Aravamudan <email address hidden> Tue, 04 Oct 2016 11:45:56 -0700

Changed in libwebp (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.