Fix the TEST variable when CONFIG_TESTS is not set:

This is another bug exposed by the new menu system. The TEST variable was set
inside the menu "test settings". But this menu depends on CONFIG_TESTS, and
is not executed if CONFIG_TESTS is not set. So that, the TEST variable was
not set if CONFIG_TESTS was not set (while with the former menu suystem,
it was set to 0). Due to the logic in lfs.xsl, this resulted in all the
tests being run, instead of none...
Move the setting of the TEST variable outside the "test settings" menu.
This commit is contained in:
Pierre Labastie 2019-07-15 14:13:48 +00:00
parent 6622409404
commit 30a89617c4

View file

@ -795,6 +795,8 @@ depends on !BOOK_BLFS
bool "Abort the build on the first test failure"
endchoice
endmenu # test settings
config TEST
int
default "0" if !CONFIG_TESTS
@ -806,9 +808,7 @@ depends on !BOOK_BLFS
bool
default n if NO_BOMB
default y if BOMB
#--- End Test Suites
endmenu # test settings
#--- End Test Suites
#--- Package Management
config PKGMNGT