[Bug 210835] [ports][net/quagga] version 1.0.20160315 build problems
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jul 5 06:41:38 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210835
Bug ID: 210835
Summary: [ports][net/quagga] version 1.0.20160315 build
problems
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: mat at FreeBSD.org
Reporter: dgilbert at eicat.ca
Assignee: mat at FreeBSD.org
Flags: maintainer-feedback?(mat at FreeBSD.org)
Created attachment 172126
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172126&action=edit
full text of "make >& log" for quagga.
On FreeBSD-10.x (tested x=2, x=3) Quagga is failing to build. The full log of
the build is attached.
... but generally the log ends with a bunch of lines like the "Duplicate" line
below repeated and then it would seem some test failing (89 instead of 92)
Duplicate CLI Function: no_match_ip_address_prefix_list_val_cmd
From cli: "no match ip address prefix-list WORD" to New cli: "no match
ip address prefix-list WORD"
Original Protocol: VTYSH_RIPD to New Protocol: VTYSH_ZEBRA
Expected 89 command line stomps, but got 92 instead
Makefile:766: recipe for target 'vtysh_cmd.c' failed
gmake[4]: *** [vtysh_cmd.c] Error 92
gmake[4]: Leaving directory
'/usr/ports/net/quagga/work/quagga-1.0.20160315/vtysh'
Makefile:461: recipe for target 'all-recursive' failed
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory '/usr/ports/net/quagga/work/quagga-1.0.20160315'
Makefile:393: recipe for target 'all' failed
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory '/usr/ports/net/quagga/work/quagga-1.0.20160315'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/net/quagga
*** Error code 1
Stop.
make: stopped in /usr/ports/net/quagga
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list