z-logo
Premium
The Linux kernel: a case study of build system variability
Author(s) -
Nadi Sarah,
Holt Ric
Publication year - 2014
Publication title -
journal of software: evolution and process
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.371
H-Index - 29
eISSN - 2047-7481
pISSN - 2047-7473
DOI - 10.1002/smr.1595
Subject(s) - linux kernel , computer science , source code , software , operating system , kernel (algebra) , code (set theory) , file system , software versioning , system call , software bug , programming language , set (abstract data type) , mathematics , combinatorics
SUMMARY Although build systems control what code gets compiled into the final built product, they are often overlooked when studying software variability. The Linux kernel is one of the biggest open source software systems supporting variability and contains over 10,000 configurable features described in its Kconfig files. To understand the role of the build system in variability implementation, we use Linux as a case study. We study its build system, Kbuild , and extract the variability constraints in its Makefiles. We first provide a quantitative analysis of the variability in Kbuild . We then study how the variability constraints in the build system affect variability anomalies detected in Linux. We concentrate on dead and undead artifacts, and by extending previous work, we show that considering build system variability constraints allows more anomalies to be detected. We provide examples of such anomalies on both the code block and source file level. Our work shows that Kbuild contains a large percentage of the variability information in Linux, so it should not be ignored during variability analysis. Nonetheless, the anomalies we find suggest that variability on the file level in Kbuild is consistent with Kconfig , whereas the constraints on the code level are harder to keep consistent with both Kbuild and Kconfig . Copyright © 2013 John Wiley & Sons, Ltd.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here