All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Akhilesh Nema <nemaakhilesh@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/radvd: bump version to 2.20
Date: Tue, 04 Feb 2025 09:06:57 +0100	[thread overview]
Message-ID: <87r04eqgke.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250109080130.759117-1-nemaakhilesh@gmail.com> (Akhilesh Nema's message of "Thu, 9 Jan 2025 00:01:30 -0800")

>>>>> "Akhilesh" == Akhilesh Nema <nemaakhilesh@gmail.com> writes:

 > - Updated radvd dependencies.
 > Changelog:
 > https://github.com/radvd-project/radvd/blob/v2.20/CHANGES

 > Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
 > ---
 >  package/radvd/Config.in  | 3 +++
 >  package/radvd/radvd.hash | 4 ++--
 >  package/radvd/radvd.mk   | 4 ++--
 >  3 files changed, 7 insertions(+), 4 deletions(-)

 > diff --git a/package/radvd/Config.in b/package/radvd/Config.in
 > index f1df0c3cb8..4149683fc9 100644
 > --- a/package/radvd/Config.in
 > +++ b/package/radvd/Config.in
 > @@ -1,6 +1,9 @@
 >  config BR2_PACKAGE_RADVD
 >  	bool "radvd"
 >  	depends on BR2_USE_MMU # fork()
 > +	depends on !BR2_STATIC_LIBS  # libbsd
 > +	depends on BR2_TOOLCHAIN_HAS_THREADS  # libbsd
 > +	select BR2_PACKAGE_LIBBSD

libbsd also depends on wchar and BR2_PACKAGE_LIBSECCOMP_ARCH_SUPPORTS,
so I added that and propagated to libvirt which selects radvd and
committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-02-04  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  8:01 [Buildroot] [PATCH 1/1] package/radvd: bump version to 2.20 Akhilesh Nema
2025-02-04  8:06 ` Peter Korsgaard [this message]

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=87r04eqgke.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=nemaakhilesh@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.