From: akuster808 <akuster808@gmail.com>
To: c.finck@enlyze.com
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] wireguard fails with "exports duplicate symbol blake2s_final (owned by kernel)" in latest poky / meta-openembedded #dunfell
Date: Wed, 3 Aug 2022 13:24:22 -0700 [thread overview]
Message-ID: <0b50f8da-dee0-4060-b9b5-f488df13d46c@gmail.com> (raw)
In-Reply-To: <CswA.1659543156268567471.pbrp@lists.yoctoproject.org>
Colin,
On 8/3/22 09:12, Colin Finck wrote:
> Hi all,
>
> I've just upgraded to latest poky and meta-openembedded and deployed a build to one of our devices.
> Unfortunately, wireguard no longer works. It fails with
>
> wireguard: exports duplicate symbol blake2s_final (owned by kernel)
This wireguard commit appears to address the issue.
https://git.zx2c4.com/wireguard-linux-compat/commit/?id=52978fcc265c472773b0b334d31705573ae8cb98
can you try this and send a patch if it works?
-armin
>
> when the module is loaded.
>
> Judging from the message, it looks like https://git.yoctoproject.org/poky/commit/?h=dunfell&id=387d23c02ea0e59ea31d52a40917556648389e96 is related.
> Could someone have a look?
>
> Thanks!
>
> Colin
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#57771): https://lists.yoctoproject.org/g/yocto/message/57771
> Mute This Topic: https://lists.yoctoproject.org/mt/92795671/3616698
> Mute #dunfell:https://lists.yoctoproject.org/g/yocto/mutehashtag/dunfell
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [akuster808@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2022-08-03 20:26 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 ` akuster808 [this message]
2022-08-31 14:32 ` Colin Finck
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=0b50f8da-dee0-4060-b9b5-f488df13d46c@gmail.com \
--to=akuster808@gmail.com \
--cc=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).