[lkml]   [2012]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectKconfig and toolchain dependencies
    Right now, we don't have a good way to encode toolchain dependencies in
    Kconfig. This makes it hard to add optional features which depend on
    newer toolchain features.

    If we just add them, then it breaks all*config and randconfig on
    platforms with the older toolchains unless the user manually adds
    exclusion rules. This is bad for testing.

    It seems relatively straightforward to do if we were to manifest some
    CONFIG_ variables based on the target toolchain, e.g.


    ... and perhaps do other tests. I suspect we would run the tests less
    frequently than what we do right now with the tests embedded in the

    Does anyone have a feel for if this would be a good addition, and if so
    where it best fits into the chain?


    H. Peter Anvin, Intel Open Source Technology Center
    I work for Intel. I don't speak on their behalf.

     \ /
      Last update: 2012-02-03 22:31    [W:0.021 / U:3.872 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site