| Summary: | Building a kernel (Fedora way) not using our config file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Djam <djamolsky> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | a.badger, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 13:57:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Djam
2011-11-25 14:42:55 UTC
I don't see anything here that looks like an issue in the rpmdevtools package. I'm not sure what component this should be filed against, but moving to kernel based on the "I think there is something wrong in the ~/rpmbuild/SPECS/kernel.spec file." sentence. Thanks for your quick reply. The kernel.spec file is the default one (I don't know which package or action provided it). The only updated parameter is the "buildid" entry. For sure, there is something wrong in it. The wiki steps seem to be slightly out-of-date. What does `uname -m` return on whatever machine you are running this on? The config file gets generated from the various bits and pieces (config-*) in the source directory. If you want to override things, just replace the empty config-local file with a set of config options you want to override. (In reply to comment #3) > The wiki steps seem to be slightly out-of-date. I think so. > What does `uname -m` return on whatever machine you are running this on? i686 (In reply to comment #5) > (In reply to comment #3) > > The wiki steps seem to be slightly out-of-date. > > I think so. > > > What does `uname -m` return on whatever machine you are running this on? > > i686 That isn't going to work at all. There are 2 32-bit config files that get sourced during the build. config-x86-32-generic is the primary one, and config-i686-PAE is the config for a PAE kernel. I'll update the build steps to remove a bunch of cruft. As Chuck says in comment #4, small overrides can just go into config-local I've updated the steps a bit on the wiki. Please follow again and see if they clear up the issue. (In reply to comment #7) > I've updated the steps a bit on the wiki. Please follow again and see if they > clear up the issue. I have done several tests using config-local and yes, it works perfectly like that (confirmed by using an empty config file with make allnoconfig and a normal one). (In reply to comment #8) > (In reply to comment #7) > > I've updated the steps a bit on the wiki. Please follow again and see if they > > clear up the issue. > > I have done several tests using config-local and yes, it works perfectly like > that > (confirmed by using an empty config file with make allnoconfig and a normal > one). Great. Thanks for pointing out the stale documentation. (In reply to comment #7) > I've updated the steps a bit on the wiki. Please follow again and see if they > clear up the issue. I have just checked the wiki: http://fedoraproject.org/wiki/Building_a_custom_kernel (I have used your advice without reading the wiki...). I do not see your updates, especially this part: ################################################## Configure Kernel Options [...] 6. Copy the config file to ~/rpmbuild/SOURCES/: cp .config ~/rpmbuild/SOURCES/config-`uname -m` # It has to be cp .config ~/rpmbuild/SOURCES/config-local ################################################## (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > I've updated the steps a bit on the wiki. Please follow again and see if they > > > clear up the issue. > > > > I have done several tests using config-local and yes, it works perfectly like > > that > > (confirmed by using an empty config file with make allnoconfig and a normal > > one). > > Great. Thanks for pointing out the stale documentation. Sorry, forgot my last comment. I have read too quickly, thanks for your help and the wiki update. |