All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] package/batman-adv: bump version to 2021.0
Date: Sun, 14 Mar 2021 22:18:09 +0100	[thread overview]
Message-ID: <20210314221809.618a8d72@gmx.net> (raw)
In-Reply-To: <20210314124249.GW2737665@scaer>

Hello Christian, Yann,

On Sun, 14 Mar 2021 13:42:49 +0100, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Christian, Peter, All,
>
> On 2021-03-12 15:51 -0800, Christian Stewart spake thusly:
> > On Fri, Mar 12, 2021 at 2:09 PM Peter Seiderer <ps.report@gmx.net> wrote:
> > > > On Thu, Mar 11, 2021 at 1:08 PM Peter Seiderer <ps.report@gmx.net> wrote:
> > > > > -BATMAN_ADV_VERSION = 2019.3
> > > > > +BATMAN_ADV_VERSION = 2021.0
> > > > I get build errors against 2 different device kernels (x86_64 and pi4):
> [--SNIP--]
> > > For me the update fixed the compile for RPi4_64 ;-), can you share your
> > > defconfig(s)?
> > OK, I see what happened here. I just ran "make batman-adv" in an
> > existing tree without enabling the Kconfig options.
> >
> > The problem is when batman adv protocol version 5 is not enabled:
> >
> > BR2_PACKAGE_BATMAN_ADV=y
> > # BR2_PACKAGE_BATMAN_ADV_DEBUG is not set
> > # BR2_PACKAGE_BATMAN_ADV_NC is not set
> > # BR2_PACKAGE_BATMAN_ADV_BATMAN_V is not set
> >
> > That's causing the "batadv_v_init" undefined errors.
>
> So is this an actual issue that still needs to be addressed, or can the
> patch be applied now?

I can confirm the compile failure in case BR2_PACKAGE_BATMAN_ADV_BATMAN_V is
not enabled...., but the buildroot config still states it is 'exerpimental':


	config BR2_PACKAGE_BATMAN_ADV_BATMAN_V
        	bool "enable B.A.T.M.A.N. V protocol (experimental)"

According to [1] CONFIG_BATMAN_ADV_BATMAN_V option is enabled by default
since 2018.2 (and it seems compile without is not tested very carefully),
maybe time to drop the buildroot config option and always enable
CONFIG_BATMAN_ADV_BATMAN_V?

But will take a deeper look at the source code if the failure is fixable
(or post an upstream failure report)...

Regards,
Peter


https://git.open-mesh.org/batman-adv.git/blob/HEAD:/CHANGELOG.rst#l174

>
> Regards,
> Yann E. MORIN.
>

  reply	other threads:[~2021-03-14 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 21:08 [Buildroot] [PATCH v1 1/2] package/batctl: bump version to 2021.0 Peter Seiderer
2021-03-11 21:08 ` [Buildroot] [PATCH v1 2/2] package/batman-adv: " Peter Seiderer
2021-03-12 21:59   ` Christian Stewart
2021-03-12 22:09     ` Peter Seiderer
2021-03-12 23:51       ` Christian Stewart
2021-03-14 12:42         ` Yann E. MORIN
2021-03-14 21:18           ` Peter Seiderer [this message]
2021-03-14 21:48             ` Yann E. MORIN
2021-03-14 22:39               ` Peter Seiderer
2021-03-16 21:09   ` Yann E. MORIN
2021-03-12 21:19 ` [Buildroot] [PATCH v1 1/2] package/batctl: " Christian Stewart
2021-03-16 21:09 ` Yann E. MORIN

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=20210314221809.618a8d72@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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.