On Thu, Feb 8, 2018 at 9:19 AM, Masahiro Yamada
wrote:
>
> Should this be checked?
> Or, is it just "Don't do it" thing?
I think it's probably a "Don't do it".
In fact, maybe we should just make it very explicit that you need to
re-run "make *config" by hand if
On Thu, Feb 8, 2018 at 9:19 AM, Masahiro Yamada
wrote:
>
> Should this be checked?
> Or, is it just "Don't do it" thing?
I think it's probably a "Don't do it".
In fact, maybe we should just make it very explicit that you need to
re-run "make *config" by hand if you have updated your compiler.
2018-02-09 1:19 GMT+09:00 Masahiro Yamada :
> Moving compiler option tests to Kconfig means you need to re-run
> Kconfig when you update your compiler. All CC_HAS_... symbols
> and other symbols that depend on them must be re-calculated.
>
> It will be nice to
2018-02-09 1:19 GMT+09:00 Masahiro Yamada :
> Moving compiler option tests to Kconfig means you need to re-run
> Kconfig when you update your compiler. All CC_HAS_... symbols
> and other symbols that depend on them must be re-calculated.
>
> It will be nice to detect the compiler update and
Moving compiler option tests to Kconfig means you need to re-run
Kconfig when you update your compiler. All CC_HAS_... symbols
and other symbols that depend on them must be re-calculated.
It will be nice to detect the compiler update and automatically
invoke silentoldconfig.
This can be done by
Moving compiler option tests to Kconfig means you need to re-run
Kconfig when you update your compiler. All CC_HAS_... symbols
and other symbols that depend on them must be re-calculated.
It will be nice to detect the compiler update and automatically
invoke silentoldconfig.
This can be done by
6 matches
Mail list logo