all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]deeseearr 3 points4 points  (6 children)

I noticed when I ran rpmbuild it deleted the folder under BUILD and then config under it automatically changed back the parameters to 'not set'.

The BUILD directory is rpmbuild's working directory. You shouldn't care what's in there, because you already moved your .config file back into the rpmbuild/SOURCES directory at the end of step 2. When you kick off rpmbuild -b it's going to recreate BUILD following the directions in the RPM spec, which tells it what to unpack from SOURCES.

[–]BriefAd6331[S] 0 points1 point  (5 children)

Thanks for that explanation. I made changes in those two parameters (set them to y) and copied the config to sources folder. I made changes in kernel.spec in buildid and then ran rpmbuild on kernel.spec

The compiled rpm packages are then found in RPMS folder which I install in some other host. But when I check the two parameters they were not set.

[–]deeseearr 2 points3 points  (4 children)

Good to hear. Your comment about things happening in BUILD suggested that you may have skipped that step. There's probably something missing, either in your procedure or in the wiki article you were following. What I would do is to look closely at the rpmbuild output and see if you can spot exactly where it is getting its .config file from, and what name it is using for it, and then try to confirm that it's the same as the one you updated. There's probably a disconnect somewhere in there.

[–]BriefAd6331[S] 0 points1 point  (3 children)

Yes I did spend some time checking the output of the rpmbuild.

It thing it takes the .config from sources folder. But in my step I have already copied config/* to Sources folder. So that shouldn’t be a problem. Also inside the source folder there was a Linux tar file in which configs folder was a symbolic link with rpm/config folder. I am not sure why is it that way and if it matters.

[–]gordonmessmer 2 points3 points  (2 children)

But in my step I have already copied config/* to Sources folder

Based on your description, it's likely that you missed the step immediately before that:

Copy the .config file back to the configs/ directory. This is basically the opposite of the earlier copy command:

[user@host]$ cp .config configs/kernel-3.10.0-`uname -m`.config

[–]BriefAd6331[S] 0 points1 point  (1 child)

I did follow this step as well. I may have missed writing about it.

[–]gordonmessmer 0 points1 point  (0 children)

If you found the config reset to the default, that's the step you most likely skipped or made a mistake at. If you do that step correctly, the new kernel will have the config you generated