All of lore.kernel.org
 help / color / mirror / Atom feed
From: veilleux.cedric@gmail.com
To: Steve Sakoman <sakoman@gmail.com>
Cc: Marek Belisko <marek.belisko@gmail.com>,
	Khem Raj <raj.khem@gmail.com>,  akuster <akuster808@gmail.com>,
	 openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] wireguard-module broken in dunfell
Date: Fri, 9 Oct 2020 15:40:24 -0400	[thread overview]
Message-ID: <CA+Xfe4Fs7H5C12kY=GTiDbSxwNNzg07vceMmPonqXS-ucTyyFw@mail.gmail.com> (raw)
In-Reply-To: <CAGDS+nmT-nLT1Kj713ihDAGtwU2361OHmaD7+Hhoii0PReKgQg@mail.gmail.com>

> > > Oh right, it got backported it dunfell recently hmm
> > Can we please revert backport so we have working wireguard again? Thanks.
>
> I'll revert this in oe-core dunfell.
>
> To be sure I see requests like this in the future it would be best to
> copy the oe-core list and/or myself.

My understanding is that the change that causes the problem is in poky
/ package.bbclass

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=87c9d296357638082f5a7131a87365285fc813c4

If I revert this commit wireguard builds fine.

I don't understand why though.

  reply	other threads:[~2020-10-09 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  6:33 wireguard-module broken in dunfell Marek Belisko
2020-10-06 17:19 ` veilleux.cedric
2020-10-06 17:56   ` [oe] " Khem Raj
2020-10-06 18:20   ` akuster
2020-10-06 18:22     ` Khem Raj
2020-10-06 19:04       ` Marek Belisko
2020-10-06 19:20         ` Khem Raj
2020-10-09 18:19           ` Marek Belisko
2020-10-09 19:14             ` Steve Sakoman
2020-10-09 19:40               ` veilleux.cedric [this message]
2020-10-13  6:06               ` c.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='CA+Xfe4Fs7H5C12kY=GTiDbSxwNNzg07vceMmPonqXS-ucTyyFw@mail.gmail.com' \
    --to=veilleux.cedric@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=marek.belisko@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=sakoman@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.