Key Points for wider discussion =============================== * 11.10 Android Pre Release 1 is built and tested: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AnpUtxWjZbP9dGFDUk... * The Monkey test for Android in LAVA is ready for deployment.
Team Highlights =============================== * Rebasing the Snowball GLK 3.0 Kernel on linaro-android.git is ongoing. * The file transfer tool lrzsz has been ported to Android. * Good progress on creating an arm-linux-androideab-* toolchain. * The ffmpeg library and x264 video encoder has been added to all builds. * Good progress on enabling support for ARM Development Studio 5. * Good progress on having Android camera app working with UVC camera. * Good progress on Audio Playback and Recording on Pnadaboard. * Strict-aliasing violations in 2.3.5 have been fixed. * Good progress on making Origen WLAN and Ethernet work.
Miscellaneous ===============================
Bugs fixed =============================== * #868550, #868479, #859974
Blueprints =============================== Milestones: https://launchpad.net/linaro-android/+milestone/11.10 Connect session Blueprints: https://blueprints.launchpad.net/sprints/lcq4.11/+specs?searchtext=linaro-pl...
On Thu, Oct 13, 2011 at 1:12 PM, Tony Mansson tony.mansson@linaro.orgwrote:
- Strict-aliasing violations in 2.3.5 have been fixed.
I remember that we disabled -Werror because of various issues ... with those strict-aliasing fixes, what is left before we can turn that on again?
On 13 October 2011 05:03, Alexander Sack asac@linaro.org wrote:
On Thu, Oct 13, 2011 at 1:12 PM, Tony Mansson tony.mansson@linaro.org wrote:
- Strict-aliasing violations in 2.3.5 have been fixed.
I remember that we disabled -Werror because of various issues ... with those strict-aliasing fixes, what is left before we can turn that on again?
The only way to know for sure is to try -- there's a couple of things gcc 4.6 warns about that gcc 4.4 silently ignored, so probably -Werror will still cause build errors, including a couple of warnings that typically don't point to serious errors, such as implicit casts between signed to unsigned types.
ttyl bero