On Wed, 27 Jun 2018 23:07:21 +0900
Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx> wrote:
> Hi.
>
>
> 2018-06-27 21:37 GMT+09:00 Michal Suchánek <msuchanek@xxxxxxx>:
> > Hello,
> >
> > in the x86 Kconfig we have this:
> >
> > # Select 32 or 64 bit
> > config 64BIT
> > bool "64-bit kernel" if "$(ARCH)" = "x86"
> > default "$(ARCH)" != "i386"
> > ---help---
> > Say yes to build a 64-bit kernel - formerly known as
> > x86_64 Say no to build a 32-bit kernel - formerly known as i386
> >
> > Since commit 104daea149c4 ("kconfig: reference environment variables
> > directly and remove 'option env='") the value of ARCH is not saved
> > in the kernel config.
>
> I think this commit is unrelated. It was just a syntax change.
This does not look like syntax only change to me:
diff --git a/init/Kconfig b/init/Kconfig
index 15aae32e0719..1217fc62ca61 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1,20 +1,12 @@
-config ARCH
- string
- option env="ARCH"
-
-config KERNELVERSION
- string
- option env="KERNELVERSION"
-
>
> Unless I am missing something,
> we have never saved ARCH in the .config in the past.
There was a config symbol defined for it before the commit removed it.
>
>
> > Since commit f467c5640c29 ("kconfig: only write '#
> > CONFIG_FOO is not set' for visible symbols") the value of 64BIT is
> > not saved if the ARCH is set i386 or x86_64 because the symbol is
> > not visible.
>
> This is correct.
>
> It was discussed a few weeks ago.
>
> https://lkml.org/lkml/2018/6/5/847
>
>
> > There is a number of ways to hack this particular case to work.
> >
> > However, there is a more general problem with this. Some config
> > options may depend on the environment, may not be saved, and the
> > environment is not saved either.
>
> Which environment variables in particular are in your mind?
Any that is used in Kconfig.
>
> As for ARCH, you need to pass the same ARCH as you used for building
> the kernel. (For native building, you do not have to pass ARCH
> explicitly, though.)
Except if you do pass it to make config you may need to pass it to to
make later as well.
>
> As for CC, HOSTCC, etc.
> yes, these are new 'unsaved' environments.
>
> CONFIG options now depend on the compiler.
> This is the concept suggested by Linus Torvalds.
>
>
> > So in the end all the infrastructure with symlinks
> > from module directory pointing to the kernel source and object
> > directory is useless. To interpret the config stored there you need
> > the environment and that is not saved anywhere. So if you try to
> > build out-of-tree module it might end up reconfiguring your kernel
> > and producing useless modules.
>
> No. out-of-tree module building never ever re-configures the kernel.
It does implicitly because the config values depend on environment that
is not saved and the values themselves are not saved either. If that
happens to expose a new variable it is even explicitly reconfigured.
>
> out-of-tree modules are built with exactly the same configuration
> as used for the kernel.
It is not true. And that is the problem. You need the config file and
dump of the environment passed to the make command at configuration
time to get the exact same configuration. The environment is not saved
anywhere, though.
Thanks
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
