Mir

cmake/MirCommon.cmake fails in detecting that valgrind is not installed

Bug #1195590 reported by Thomas Voß
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Unassigned

Bug Description

The build setup should detect if valgrind is not installed and disable all tests requiring valgrind to run.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Note that it's only on armhf:

i386 is fine:
https://launchpadlibrarian.net/143541061/buildlog_ubuntu-saucy-i386.mir_0.0.6%2B13.10.20130627ubuntu.unity.next-0ubuntu1_UPLOADING.txt.gz

armhf:
https://launchpadlibrarian.net/143544949/buildlog_ubuntu-saucy-armhf.mir_0.0.6%2B13.10.20130627ubuntu.unity.next-0ubuntu1_FAILEDTOBUILD.txt.gz

Changed in mir:
status: New → Triaged
Revision history for this message
Alberto Aguirre (albaguirre) wrote :

Looking at the current MirCommon.cmake, it seems this has already been fixed.

Changed in mir:
status: Triaged → 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.