Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Joakim Tallinger <>
Subject: Building Directly In Tree with Buildroot
Date: Sun, 22 May 2022 13:15:11 +0200	[thread overview]
Message-ID: <> (raw)


I’m using Buildroot to build a custom linux kernel (4.14.185) for an embedded system, for which I now want to add Wireguard to. I have one config for initrd and another one for rootfs.

I added  “BR2_PACKAGE_WIREGUARD_LINUX_COMPAT” to initrd and “BR2_PACKAGE_WIREGUARD_TOOLS” to rootfs. It downloads the source and builds it accordingly. I can see the module is there before initrd image is created, but since system is booted with initrd, and then rootfs is mounted I can’t access the module with modprobe. To my understanding I need to solve this by building Wireguard in tree (i.e where module is always active)?

Which brings me to the question on how to apply the kernel tree script “”. I can manually navigate to the linux src directory and run it, but that won’t work as part of the Buildroot process.

I guess I need to add a pre-build step to run the script to patch the linux src, then add CONFIG_WIREGUARD=y to my custom kernel config. Would this be the correct way to do it? Or is there some easier way to manage it?

Br, Joakim 

                 reply	other threads:[~2022-05-26 10:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: Building Directly In Tree with Buildroot' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).