From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] package/batman-adv: fix compile with BR2_PACKAGE_BATMAN_ADV_BATMAN_V disabled
Date: Tue, 16 Mar 2021 19:19:35 +0100 [thread overview]
Message-ID: <20210316191935.6cfb47fa@gmx.net> (raw)
In-Reply-To: <CA+h8R2p+uepuOOpG=QbZ+y4bEzQZ4eL6BQU1wScyqXfVXALYZA@mail.gmail.com>
Hello Christian,
On Mon, 15 Mar 2021 18:45:20 -0700, Christian Stewart <christian@paral.in> wrote:
> Hi Peter,
>
> On Mon, Mar 15, 2021 at 2:50 PM Peter Seiderer <ps.report@gmx.net> wrote:
> > On Mon, 15 Mar 2021 14:00:38 -0700, Christian Stewart <christian@paral.in> wrote:
> > > On Sun, Mar 14, 2021 at 3:32 PM Peter Seiderer <ps.report@gmx.net> wrote:
> > > >
> > > > The given 'CONFIG_BATMAN_ADV_BATMAN_V=' is enough to trigger the wrong
> > > > code compile path in net/batman-adv/bat_v.h missing the static inline
> > > > dummy implementations.
> > > >
> > > > Fixes:
> > >
> > > Unfortunately after applying this commit it still breaks.
> > >
> > > I confirmed that the CONFIG_BATMAN_ADV_BATMAN_V is not being set now.
> > >
> > >
> > > CONFIG_BATMAN_ADV=m
> > > CONFIG_BATMAN_ADV_BLA=y
> > > CONFIG_BATMAN_ADV_DAT=y
> > > CONFIG_BATMAN_ADV_MCAST=y
> > > M=build/batman-adv-2021.0/net/batman-adv
> > > make modules
> > >
> > > [snip]
> > >
> > > MODPOST /build/batman-adv-2021.0/net/batman-adv/Module.symvers
> > > ERROR: modpost: "batadv_v_mesh_free" undefined!
> > > ERROR: modpost: "batadv_v_mesh_init" undefined!
> > > ERROR: modpost: "batadv_v_hardif_init" undefined!
> > > ERROR: modpost: "batadv_v_init" undefined!
> >
> > Mind to share your defconfig (which cross-compiler)?
> >
> > Did you do a complete re-build of the batman-adv-2021.0
> > package (rm -rf build/batman-adv-2021.0 && make batman-adv)?
>
> Buildroot toolchain,
>
> BR2_x86_64=y
> BR2_TOOLCHAIN=y
> BR2_TOOLCHAIN_USES_GLIBC=y
> BR2_TOOLCHAIN_BUILDROOT=y
> BR2_BINUTILS_VERSION_2_35_X=y
> BR2_GCC_VERSION_10_X=y
> BR2_PACKAGE_BATMAN_ADV=y
>
> Yes, deleted the build/batman-adv* dir and fully re-built, and
> confirmed that it was not setting the BATMAN_ADV_V flag anymore.
O.k, using the following defconfig I get the same failure:
BR2_x86_64=y
BR2_GCC_VERSION_10_X=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
BR2_PACKAGE_BATMAN_ADV=y
My RPi4 test case had an RPi4 linux kernel already enabling the build-in
batman-adv module inclusive batman-v...
Hopefully fixed this time for real with
https://patchwork.ozlabs.org/project/buildroot/patch/20210316181429.30804-1-ps.report at gmx.net/
https://patchwork.ozlabs.org/project/buildroot/patch/20210316181429.30804-2-ps.report at gmx.net/
and a note about the linux mainline kernel module added with
https://patchwork.ozlabs.org/project/buildroot/patch/20210316181429.30804-3-ps.report at gmx.net/
Regards,
Peter
>
> Thanks,
> Christian
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-03-16 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 22:32 [Buildroot] [PATCH v1 1/2] package/batman-adv: fix compile with BR2_PACKAGE_BATMAN_ADV_BATMAN_V disabled Peter Seiderer
2021-03-14 22:32 ` [Buildroot] [PATCH v1 2/2] package/batman-adv: enable B.A.T.M.A.N. V protocol by default Peter Seiderer
2021-03-15 19:59 ` Yann E. MORIN
2021-03-15 20:49 ` Christian Stewart
2021-03-15 22:12 ` Peter Seiderer
2022-07-24 21:26 ` Arnout Vandecappelle
2021-03-15 19:53 ` [Buildroot] [PATCH v1 1/2] package/batman-adv: fix compile with BR2_PACKAGE_BATMAN_ADV_BATMAN_V disabled Yann E. MORIN
2021-03-15 21:00 ` Christian Stewart
2021-03-15 21:50 ` Peter Seiderer
2021-03-16 1:45 ` Christian Stewart
2021-03-16 18:19 ` Peter Seiderer [this message]
2021-03-23 17:26 ` Peter Korsgaard
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=20210316191935.6cfb47fa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox