No problem, thanks for fixing it!
On 11/12/24 6:02 AM, Daniel Baumann wrote:
On 11/10/24 09:54, Daniel Baumann wrote:
then I'm clearly missing something
the build-profile logic in the package was "weird" (default off and
needs a positive to enable it, rather than default on and a negative to
d
On 11/10/24 09:54, Daniel Baumann wrote:
> then I'm clearly missing something
the build-profile logic in the package was "weird" (default off and
needs a positive to enable it, rather than default on and a negative to
disable it). I've harmonized that now.
thanks for help getting there!
Regards,
Alright, thanks. Just for reference as to what I did. I followed this
guide on the frr website and used the debian repo package for libyang2
as it's a new enough version when building on sid
https://docs.frrouting.org/projects/dev-guide/en/latest/building-frr-for-debian12.html
On 11/10/24 12:5
Hi,
On 11/10/24 09:28, Scoopta wrote:
> I built the current frr master with debian sid and gcc
> 14 successfully, including both pimd and pim6d.
then I'm clearly missing something (jftr, I've tried building what is in
frr/pimd). I'll check again..
Regards,
Daniel
Hey Daniel,
I'm slightly confused here. The frr pimd code last had a commit 2 weeks
ago with frequent commits before then. Just to make sure I wasn't
missing something I built the current frr master with debian sid and gcc
14 successfully, including both pimd and pim6d. Additionally pimd is
a
close 1071653
thanks
Hi,
thank you for your report. It seems that pimd in frr upstream sources
are not really maintained - the code doesn't build with any recent gcc
and would need some care.
Until this happens upstream, we can't/it doesn't make sense to (try) to
enable it in Debian, hence I'm c
6 matches
Mail list logo
