From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Dario Binacchi <dariobin@libero.it>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libmnl: fix build failure
Date: Sun, 21 May 2023 22:00:26 +0200 [thread overview]
Message-ID: <20230521200026.GC621937@scaer> (raw)
In-Reply-To: <CABGWkvo-xhQAJWc2+Jqn=ni-kzH7fqqzOnzwkGLVhe7_wn2GWQ@mail.gmail.com>
Dario, All,
On 2023-05-21 20:36 +0200, Dario Binacchi spake thusly:
> On Sun, May 21, 2023 at 5:16 PM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2023-05-21 17:10 +0200, Yann E. MORIN spake thusly:
> > > On 2023-05-20 23:01 +0200, Dario Binacchi spake thusly:
> > > > The added patch is an adaptation of the one submitted to the libmnl
> > > > project.
> > > >
> > > > Fixes:
> > > > - http://autobuild.buildroot.net/results/36c1619c8b02efeaf9caebae8bb5c3eb8a26238b/
> > > > - http://autobuild.buildroot.net/results/15f6dc103eec7bdeb5020acbc0ae99dc97c00e4e/
> > > Those failures are due to improper dependency on kernel headers:
> > Still, the proper way is to add a dependency on kernel headers >= 4.11
> > for the libmnl examples.
> In the libmnl repository, there are commits adding kernel headers to avoid
> dependency issues. The CAN header was missing because the added example
> was the first one related to CAN. It's worth noting that even the
> can-utils package
> synchronizes its internal headers with the kernel headers whenever they change.
> In fact, in the can-utils package in buildroot, there are no
> dependencies on kernel
> headers. If you agree, I would wait to verify if the patch I submitted
> to libmnl is
> accepted. If it is, we can apply only that patch.
>
> What do you think?
I think that I should not have applied the CAN example patch, as it was
clearly a feature patch; I only applied it because the patch was already
applied upstream, so it was a patch we would not have to carry forever,
*and* examples are just that, examples, and are not needed for a
functional package, *and* it looked prety self-contained.
However, it b reaks the build, so this is not nice.
So, my position is that we should really add the dependency on kernel
headers in master, and if/when upstream applies the headers include
patch, then we can see to relax the restriction.
A slightly less restrictive solution would be to only include the CAN
example when the toolchain headers are fitting, e.g. something like
(with full reorganisation of examples which I refrained from doing when
applying your previous patch 271745c37a04, but now we'd need it to be
even cleaner...):
LIBMNL_EXAMPLES_genl = genl-family-get genl-group-events
LIBMNL_EXAMPLES_kobject = kobject-event
LIBMNL_EXAMPLES_netfilter = \
nfct-create-batch \
nfct-daemon \
nfct-dump \
nfct-event \
nf-log \
nf-queue
LIBMNL_EXAMPLES_rtnl = \
rtnl-addr-add \
rtnl-addr-dump \
rtnl-link-dump \
rtnl-link-dump2 \
rtnl-link-dump3 \
rtnl-link-event \
rtnl-link-set \
rtnl-neigh-dump \
rtnl-route-add \
rtnl-route-dump \
rtnl-route-event
ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_11),y)
LIBMNL_EXAMPLES_rtnl += rtnl-link-can
endif
LIBMNL_EXAMPLES_INSTALL_TARGETS = \
$(foreach t, \
genl kobject netfilter rtnl, \
$(addprefix examples/$(t)/,$(LIBMNL_EXAMPLES_$(t))))
Regards,
Yann E. MORIN.
> Thanks and regards,
> Dario
> >
> > Regards,
> > Yann E. MORIN.
> >
> > --
> > .-----------------.--------------------.------------------.--------------------.
> > | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> > | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
> > | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
> > '------------------------------^-------^------------------^--------------------'
>
>
>
> --
>
> Dario Binacchi
>
> Senior Embedded Linux Developer
>
> dario.binacchi@amarulasolutions.com
>
> __________________________________
>
>
> Amarula Solutions SRL
>
> Via Le Canevare 30, 31100 Treviso, Veneto, IT
>
> T. +39 042 243 5310
> info@amarulasolutions.com
>
> www.amarulasolutions.com
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-05-21 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 21:01 [Buildroot] [PATCH 1/1] package/libmnl: fix build failure Dario Binacchi
2023-05-21 15:10 ` Yann E. MORIN
2023-05-21 15:16 ` Yann E. MORIN
2023-05-21 18:36 ` Dario Binacchi
2023-05-21 20:00 ` Yann E. MORIN [this message]
2023-05-22 10:32 ` Dario Binacchi
2023-05-23 16:29 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2023-05-23 17:31 Dario Binacchi
2023-05-24 19:08 ` 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=20230521200026.GC621937@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=dariobin@libero.it \
/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.