Hello,
I am trying to build the fedora kernel with the muqss patch and the patches for the surface devices. To start I tried to build it only with the muqss patch. So tried as well with fedpkg as well as a plain rpmbuild but both hang at the same stage. I enpacked the kernel.src.rpm, fetched the latest muqss patch and added it in the kernel.spec. Also I did set %define with_baseonly 1 to build only non-debug x86_64 Trying to build the kernel with rpmbuild -ba kernel.spec will fail at the stage of process_configs.sh that compains about config options being unset (and .git/rebase-apply/patch:7590: space before tab in indent. cpu = i; .) So I try to add them to all config's but when building I get: Error: Mismatches found in configuration files Found CONFIG_RQ_ALL=is not set after generation, had CONFIG_RQ_ALL=n in Source tree Found CONFIG_RQ_SMP=is not set after generation, had CONFIG_RQ_SMP=n in Source tree Found CONFIG_RQ_SMT=is not set after generation, had CONFIG_RQ_SMT=n in Source tree Found CONFIG_RQ_NONE=is not set after generation, had CONFIG_RQ_NONE=n in Source tree
What is the correct way to build the fedora kernel with a custom patch added?
* tried this as well https://fedoramagazine.org/building-fedora-kernel/
Thanks in advance. Damian
On Sat, Sep 7, 2019 at 7:02 PM Damian Ivanov damianatorrpm@gmail.com wrote:
Hello,
I am trying to build the fedora kernel with the muqss patch and the patches for the surface devices. To start I tried to build it only with the muqss patch. So tried as well with fedpkg as well as a plain rpmbuild but both hang at the same stage. I enpacked the kernel.src.rpm, fetched the latest muqss patch and added it in the kernel.spec. Also I did set %define with_baseonly 1 to build only non-debug x86_64 Trying to build the kernel with rpmbuild -ba kernel.spec will fail at the stage of process_configs.sh that compains about config options being unset (and .git/rebase-apply/patch:7590: space before tab in indent. cpu = i; .) So I try to add them to all config's but when building I get: Error: Mismatches found in configuration files Found CONFIG_RQ_ALL=is not set after generation, had CONFIG_RQ_ALL=n in Source tree Found CONFIG_RQ_SMP=is not set after generation, had CONFIG_RQ_SMP=n in Source tree Found CONFIG_RQ_SMT=is not set after generation, had CONFIG_RQ_SMT=n in Source tree Found CONFIG_RQ_NONE=is not set after generation, had CONFIG_RQ_NONE=n in Source tree
What is the correct way to build the fedora kernel with a custom patch added?
It looks like you are doing fine. The issue is, for config options
'CONFIG_OPTION=n' is not a valid way to turn something off, it needs to be '# CONFIG_OPTION is not set'
Justin
- tried this as well https://fedoramagazine.org/building-fedora-kernel/
Thanks in advance. Damian _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Hello Justin,
Thank you for your answer! It worked perfectly.
bash-5.0$ dmesg | grep "MuQSS CP" [ 2.253225] MuQSS CPU scheduler v0.193 by Con Kolivas.
On Sun, Sep 8, 2019 at 12:09 PM Justin Forbes jforbes@redhat.com wrote:
On Sat, Sep 7, 2019 at 7:02 PM Damian Ivanov damianatorrpm@gmail.com wrote:
Hello,
I am trying to build the fedora kernel with the muqss patch and the patches for the surface devices. To start I tried to build it only with the muqss patch. So tried as well with fedpkg as well as a plain rpmbuild but both hang at the same stage. I enpacked the kernel.src.rpm, fetched the latest muqss patch and added it in the kernel.spec. Also I did set %define with_baseonly 1 to build only non-debug x86_64 Trying to build the kernel with rpmbuild -ba kernel.spec will fail at the stage of process_configs.sh that compains about config options being unset (and .git/rebase-apply/patch:7590: space before tab in indent. cpu = i; .) So I try to add them to all config's but when building I get: Error: Mismatches found in configuration files Found CONFIG_RQ_ALL=is not set after generation, had CONFIG_RQ_ALL=n in Source tree Found CONFIG_RQ_SMP=is not set after generation, had CONFIG_RQ_SMP=n in Source tree Found CONFIG_RQ_SMT=is not set after generation, had CONFIG_RQ_SMT=n in Source tree Found CONFIG_RQ_NONE=is not set after generation, had CONFIG_RQ_NONE=n in Source tree
What is the correct way to build the fedora kernel with a custom patch added?
It looks like you are doing fine. The issue is, for config options 'CONFIG_OPTION=n' is not a valid way to turn something off, it needs to be '# CONFIG_OPTION is not set'
Justin
- tried this as well https://fedoramagazine.org/building-fedora-kernel/
Thanks in advance. Damian _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
On Sun, 8 Sep 2019 03:01:04 +0300 Damian Ivanov damianatorrpm@gmail.com wrote:
What is the correct way to build the fedora kernel with a custom patch added?
From an old post, modified for your use case:
I use the older rpmbuild method, so I'm not sure how that agrees with the currently recommended method. Here goes. This is long, and a lot of the details are missing.
Install the rpmbuild packages.
Run rpmbuild-setuptree to build the rpmbuild directory tree in your home directory.
Go to koji and get the kernel src.rpm
Run rpm -ivh to install it to the rpmbuild directory.
I then use screen to have a bunch of terms available, so I'm not constantly having to switch directories, but you could just switch between a bunch of virtual consoles.
Go into the ~/rpmbuild/SPECS directory. You'll see kernel.spec in there.
Run rpmbuild -bp kernel.spec to expand the source.
When it is done, go into the ~/rpmbuild/BUILD/kernel[]/linux[]/ directory. Since fedora now builds all kernels from a git repository, it is necessary to build patches for them from that git repository. It's a PITA, but necessary.
Run git add .
Run git commit -a
Just add a throwaway comment and save.
Run git status.
Everything should be up to date.
Run git config user.name "blah"
Run git config user.email "blah@blah.com"
Run git branch muqss to create a new branch for the muqss linux kernel.
Run git checkout muqss to set that as the working branch.
Patch the working branch, muqss with the muqss patch.
Run git add .
Run git commit -a.
Put in a comment and save.
Run git status to be sure the branch is clean.
Run git format-patch master
Put the resulting patch in ~/rpmbuild/SOURCES with a unique numerical prefix.
Make it look like the other patches in terms of directories at the top of the patch, give it a descriptive name, and change the subject to the descriptive name.
Put the patch name in ~/rpmbuild/SPECS/kernel.spec just before END OF PATCHES.
Run rpmbuild -bb kernel.spec
You will have the kernel rpm files in ~/rpmbuild/RPMS/x86_64
Some details might be missing, but this should get you very close.
Hello Stan
Sorry for the late reply, Gmail sent your message to spam, something about Zoho. This is already resolved thank you anyways!
On Sun, 8 Sep 2019, 17:47 stan, upaitag@zoho.com wrote:
On Sun, 8 Sep 2019 03:01:04 +0300 Damian Ivanov damianatorrpm@gmail.com wrote:
What is the correct way to build the fedora kernel with a custom patch added?
From an old post, modified for your use case:
I use the older rpmbuild method, so I'm not sure how that agrees with the currently recommended method. Here goes. This is long, and a lot of the details are missing.
Install the rpmbuild packages.
Run rpmbuild-setuptree to build the rpmbuild directory tree in your home directory.
Go to koji and get the kernel src.rpm
Run rpm -ivh to install it to the rpmbuild directory.
I then use screen to have a bunch of terms available, so I'm not constantly having to switch directories, but you could just switch between a bunch of virtual consoles.
Go into the ~/rpmbuild/SPECS directory. You'll see kernel.spec in there.
Run rpmbuild -bp kernel.spec to expand the source.
When it is done, go into the ~/rpmbuild/BUILD/kernel[]/linux[]/ directory. Since fedora now builds all kernels from a git repository, it is necessary to build patches for them from that git repository. It's a PITA, but necessary.
Run git add .
Run git commit -a
Just add a throwaway comment and save.
Run git status.
Everything should be up to date.
Run git config user.name "blah"
Run git config user.email "blah@blah.com"
Run git branch muqss to create a new branch for the muqss linux kernel.
Run git checkout muqss to set that as the working branch.
Patch the working branch, muqss with the muqss patch.
Run git add .
Run git commit -a.
Put in a comment and save.
Run git status to be sure the branch is clean.
Run git format-patch master
Put the resulting patch in ~/rpmbuild/SOURCES with a unique numerical prefix.
Make it look like the other patches in terms of directories at the top of the patch, give it a descriptive name, and change the subject to the descriptive name.
Put the patch name in ~/rpmbuild/SPECS/kernel.spec just before END OF PATCHES.
Run rpmbuild -bb kernel.spec
You will have the kernel rpm files in ~/rpmbuild/RPMS/x86_64
Some details might be missing, but this should get you very close. _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
On Mon, 9 Sep 2019 21:21:11 +0300 Damian Ivanov damianatorrpm@gmail.com wrote:
Hello Stan
Sorry for the late reply, Gmail sent your message to spam, something about Zoho. This is already resolved thank you anyways!
Yeah, I saw the reply from Justin after I sent the message. I deduced that my response was irrelevant because you must be using an in kernel patch rather than one you created yourself. Thanks for taking the time to reply.
kernel@lists.fedoraproject.org
-
Damian Ivanov -
Justin Forbes -
stan