yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Colin Finck" <c.finck@enlyze.com>
To: yocto@lists.yoctoproject.org
Subject: Re: wireguard fails with "exports duplicate symbol blake2s_final (owned by kernel)" in latest poky / meta-openembedded #dunfell
Date: Wed, 31 Aug 2022 07:32:11 -0700	[thread overview]
Message-ID: <22352.1661956331262265275@lists.yoctoproject.org> (raw)
In-Reply-To: <0b50f8da-dee0-4060-b9b5-f488df13d46c@gmail.com>

Thanks for the quick response, Armin!

After talking to Jason A. Donenfeld, it turned out that updating to the latest wireguard 1.0.x version is the only solution supported by the author. We should never maintain our own fork of wireguard 1.0.20200401, even less so considering that it's a highly security-critical component.
The major and minor version of the latest wireguard stays the same. Hence, this is even a solution for a Yocto LTS release like dunfell.

As a consequence, I'm importing the latest wireguard version in this PR: https://github.com/openembedded/meta-openembedded/pull/599

I have tested that PR and it works like a charm on latest Yocto/Poky dunfell.
Even no longer reports a "dirty" version or warns about "loading out-of-tree module taints kernel".

Colin


      reply	other threads:[~2022-08-31 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 16:12 wireguard fails with "exports duplicate symbol blake2s_final (owned by kernel)" in latest poky / meta-openembedded #dunfell Colin Finck
2022-08-03 17:46 ` Colin Finck
2022-08-03 20:24 ` [yocto] " akuster808
2022-08-31 14:32   ` Colin Finck [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=22352.1661956331262265275@lists.yoctoproject.org \
    --to=c.finck@enlyze.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).