From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] frr: Depend on elfutils
Date: Sat, 22 Jan 2022 12:30:43 +0100 [thread overview]
Message-ID: <9172cc4a-dfa5-66e4-b882-c2a74c13f861@ipfire.org> (raw)
In-Reply-To: <20220122101855.313301-2-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
Missed that change as well. Thanks for finding and fixing it.
Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
On 22/01/2022 11:18, Michael Tremer wrote:
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> lfs/frr | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/frr b/lfs/frr
> index 1af776eb6..04f1aa590 100644
> --- a/lfs/frr
> +++ b/lfs/frr
> @@ -32,9 +32,9 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = frr
> -PAK_VER = 2
> +PAK_VER = 3
>
> -DEPS =
> +DEPS = elfutils
>
> CFLAGS += -fcommon
>
next prev parent reply other threads:[~2022-01-22 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 10:18 [PATCH 1/2] libyang: Include in the core distribution Michael Tremer
2022-01-22 10:18 ` [PATCH 2/2] frr: Depend on elfutils Michael Tremer
2022-01-22 11:30 ` Adolf Belka [this message]
2022-01-22 11:28 ` [PATCH 1/2] libyang: Include in the core distribution Adolf Belka
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=9172cc4a-dfa5-66e4-b882-c2a74c13f861@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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