diff options
author | 2017-02-24 15:57:31 +0100 | |
---|---|---|
committer | 2017-02-26 10:54:39 +0100 | |
commit | d3c7687adbdc59841519ce8066e03dcb7ba0cbca (patch) | |
tree | 20920a277d24095848dbd147193a9fc7fd582999 | |
parent | end-quiz: Combine KEYWORDS questions into a single number (diff) | |
download | comrel-d3c7687adbdc59841519ce8066e03dcb7ba0cbca.tar.gz comrel-d3c7687adbdc59841519ce8066e03dcb7ba0cbca.tar.bz2 comrel-d3c7687adbdc59841519ce8066e03dcb7ba0cbca.zip |
end-quiz: Reverse the GCC question to account for different compilers
Reverse the GCC question to avoid suggesting that the package builds
only with GCC -- i.e. make it say it does not build with old gcc. This
could naturally be used to check user's awareness of other compilers.
-rw-r--r-- | recruiters/quizzes/end-quiz.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/recruiters/quizzes/end-quiz.txt b/recruiters/quizzes/end-quiz.txt index 7e1c1aa..f51d7aa 100644 --- a/recruiters/quizzes/end-quiz.txt +++ b/recruiters/quizzes/end-quiz.txt @@ -171,7 +171,7 @@ docs: devmanual docs: devmanual -16. Your package only builds with newer gcc (e.g. >gcc-4.7). +16. Your package fails to build with older versions of GCC (e.g. GCC < 4.7). How do you ensure that the user uses an appropriate compiler to build the package? Under which circumstances should you avoid this check and how? |