On Tue, Oct 25, 2016 at 06:20:16PM +0200, Max wrote: I have it on my todo list, first wanted to get libosmocore through as a confirmation that using a ./configure switch is acceptable. One point though might be build time: it is conceivable that an ASAN build hides bugs that a normal build exhibits, so we would preferably build both with and without ASAN in our jenkins build jobs. I'm not entirely sure whether all dependencies need to be built with ASAN or only the final linking of a binary is enough. For example building openbsc with all of its dependencies once with and once without ASAN would double our build matrix, yet again. In libosmocore, we once run 'make check' with ASAN and then 'make distcheck' without ASAN, which completes fairly quickly. We'll have to see what ASAN means for the other projects' gerrit build jobs. For starters, it would be great to fix the ASAN failure seen in https://jenkins.osmocom.org/jenkins/job/Osmocom_Sanitizer/ Also on my todo-list, but let's see who catches it first :) ~Neels -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte