Building kernel with fedpkg and custom config

Hello,

I've tried to build a kernel with custom config following https://fedoraproject.org/wiki/Building_a_custom_kernel

Building the kernel following that recipe works fine.

$ fedpkg clone -a kernel
$ git checkout origin/f25
edit kernel.spec
# define buildid .local > %define buildid .local

$ fedpkg local

However I can't figure out the bit with the custom config.

The instructions on the wiki say that: 
  "Enabling config options
   If there are configuration options that need to be adjusted for your build, you can add changes in the config-local file. 
   This will override anything set in the rest of the defconfigs."

I've created the .config with "make xconfig"

But there is no config-local file anywhere, copying/renaming the .config to config-local does nothing
There is a kernel-local file, copying the .config to kernel-local does nothing

I've also tried to replace the kernel-x64-86.config generated with build_configs.sh with the .config I made with make xconfig, and then tried to run fedpkg local - but that gives an error message (target for arch not found or something along those lines)

So in short, how do I build a kernel with fedpkg with a custom config? It seems that the wiki is lacking a crucial bit of information, or there's something wrong with the fedpkg system for building kernels.

regards

[Laura Abbott]

On 06/08/2017 09:18 AM, [e-mail] wrote:
> Hello,
>
> I've tried to build a kernel with custom config following https://fedoraproject.org/wiki/Building_a_custom_kernel
>
> Building the kernel following that recipe works fine.
>
> $ fedpkg clone -a kernel
> $ git checkout origin/f25
> edit kernel.spec
> # define buildid .local > %define buildid .local
>
> $ fedpkg local
>
> However I can't figure out the bit with the custom config.
>
> The instructions on the wiki say that: 
>   "Enabling config options
>    If there are configuration options that need to be adjusted for your build, you can add changes in the config-local file. 
>    This will override anything set in the rest of the defconfigs."
>
> I've created the .config with "make xconfig"
>
> But there is no config-local file anywhere, copying/renaming the .config to config-local does nothing
> There is a kernel-local file, copying the .config to kernel-local does nothing
>
> I've also tried to replace the kernel-x64-86.config generated with build_configs.sh with the .config I made with make xconfig, and then tried to run fedpkg local - but that gives an error message (target for arch not found or something along those lines)
>
> So in short, how do I build a kernel with fedpkg with a custom config? It seems that the wiki is lacking a crucial bit of information, or there's something wrong with the fedpkg system for building kernels.
>
> regards

Like all good wikis this one has gotten a bit out of date.

You should be adding configuration options to kernel-local and these
will get picked up when you build. Copying to kernel-x86-64.config
will work but you need to add

# x86_64

at the top of the file as well.

Thanks,
Laura

Hi Laura,

Thanks for the reply, and indeed it works like a charm when I put that #x86_64 header in the config file, likewise the kernel-local file also works perfectly, when I keep the header in the file.

One of the very few things I didn't try...

I would suggest updating the wiki to reflect this. and avoid stupid questions like this again. ;-) 
"If adding configuration options to the kernel-local file remember to keep the original header" or something like that.

However I stumbled upon another issue, when trying a "make localyesconfig" fedpgk fails with the message that "modules.list" is empty, which isn't surprising if it's supposed to be built without modules.

Thanks again. 
regards

[Josh Boyer]

On Fri, Jun 9, 2017 at 9:02 AM,   wrote:
> Hi Laura,
>
> Thanks for the reply, and indeed it works like a charm when I put that #x86_64 header in the config file, likewise the kernel-local file also works perfectly, when I keep the header in the file.
>
> One of the very few things I didn't try...
>
> I would suggest updating the wiki to reflect this. and avoid stupid questions like this again. ;-)

It's a wiki.  If you have a FAS account, you can contribute by
updating it yourself :).

josh
> "If adding configuration options to the kernel-local file remember to keep the original header" or something like that.
>
> However I stumbled upon another issue, when trying a "make localyesconfig" fedpgk fails with the message that "modules.list" is empty, which isn't surprising if it's supposed to be built without modules.
>
> Thanks again.
> regards
>
> kernel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Excellent suggestion, and I'd like to contribute, but I'm still something of a novice and apart from small suggestions like the above, I doubt I currently have much to contribute for real world practical application, so I haven't bothered to get a FAS account. (to be honest I don't even know what a FAS account is, just assuming it's related to the fedora project website and wiki)

But perhaps one day... perhaps someone could hire me to spend my time to go over documentation, test recipes and improve upon them to make life easier for developers, packagers, testers, and end users. ;-)

regards,