http://bugzilla.suse.com/show_bug.cgi?id=1137361 Michal Kubeček changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkubecek@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c2 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvedovati@suse.com Flags| |needinfo?(mvedovati@suse.co | |m) --- Comment #2 from Jiri Slaby --- (In reply to Marco Vedovati from comment #1)

I'm pushing the branch users/mvedovati/master/for-next with the changes to kerncvs.suse.de

This did not go through -- it is in failed tests: users/mvedovati/master/for-next (22314aaf) What went wrong? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c4 --- Comment #4 from Michal Kubeček --- This is a fallout from upstream kconfig/kbuild changes in kernel 4.17 and 4.18. With newer kernel, results of build environment tests (e.g. compiler capabilities) are also stored into .config file so that to update a config, one needs to use (almost) the same version of gcc on the same architecture as the build is going to use. Currently we are working around this by letting run_oldconfig.sh use cross compilers if installed and running it only on updated Tumbleweed. Please submit your branch under a different name (e.g. .../master/1137361), I'll run run_oldconfig.sh in the right environment on top of it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c6 Michal Kubeček changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Michal Kubeček --- (In reply to Marco Vedovati from comment #5)

Pushed to users/mvedovati/master/bsc1137361, thank you.

This won't work as expected. The kvmsmall configs are diff configs against default (pae for i586) so that listing only the options you want would end up with everything we have in default and possibly something more. That's not what we want in kvmsmall. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c8 --- Comment #8 from Michal Kubeček --- Scripts config-merge and config-diff in scripts/ subdirectory can be used to merge a diff config with the base config and to create a diff from two full configs. But in general, preferred way to update configs is using the run_oldconfig.sh script. In general, all you need is to use scripts/sequence_patch.sh to get expanded tree, switch to the directory with it and run ./run_oldconfig.sh from there, possibly with --flavor and/or -a (--arch) options. For branches based on kernel 4.17 and newer, this gets more complicated as to get correct configs, you need an up-to-date Tumbleweed system (or chroot) with cross compiler packages for architectures we build, in particular cross-{arm,aarch64,powerpc64,powerpc64le,s390x}-{gcc9,binutills} run_oldconfig.sh will use the appropriate cross compiler for the architecture if it's available. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c10 --- Comment #10 from Marco Vedovati --- (In reply to Michal Kubeček from comment #8)

Scripts config-merge and config-diff in scripts/ subdirectory can be used to merge a diff config with the base config and to create a diff from two full configs. But in general, preferred way to update configs is using the run_oldconfig.sh script.

In general, all you need is to use scripts/sequence_patch.sh to get expanded tree, switch to the directory with it and run ./run_oldconfig.sh from there, possibly with --flavor and/or -a (--arch) options.

This is what I was doing already. The problem is that when adding a new flavor, what is generated is just a delta compared to the default flavor. Having a new flavor with an empty file would be equivalent to use default. So you need to identify in the default config all the non-essential config lines that can be shaved off, and add them in the new flavor in the form of #CONFIG_... is not set" lines. This require some deep knowledge of the architecture. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c11 --- Comment #11 from Jiri Slaby --- So what is the status of this? Has this been merged yet? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137361 http://bugzilla.suse.com/show_bug.cgi?id=1137361#c13 Sascha Grunert changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sgrunert@suse.com | |) | --- Comment #13 from Sascha Grunert ---

Sascha, since Marco left recently, maybe you have more insight into this. I'd guess we currently don't need the kvmsmall flavors for s390x and arm. Is that right?

Yes, this was just a nice extra but has no strict necessity. -- You are receiving this mail because: You are on the CC list for the bug.