Bug 199401 - net-mgmt/net-snmp fails to compile with error mibII/ipv6.c:848:29 error
Summary: net-mgmt/net-snmp fails to compile with error mibII/ipv6.c:848:29 error
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Ryan Steinmetz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-12 18:14 UTC by mikhail.rokhin
Modified: 2016-02-19 23:08 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (zi)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mikhail.rokhin 2015-04-12 18:14:15 UTC 
mibII/ipv6.c:848:29 error: variable has incomplete type 'struct ifaddr'
Comment 1 Ryan Steinmetz freebsd_committer freebsd_triage 2015-09-09 19:28:34 UTC 
Context? OS? Fix?
Comment 2 commit-hook freebsd_committer freebsd_triage 2016-02-19 23:05:44 UTC 
A commit references this bug:

Author: ian
Date: Fri Feb 19 23:05:09 UTC 2016
New revision: 409215
URL: https://svnweb.freebsd.org/changeset/ports/409215

Log:
  Fix net-snmp ipv6 option handling when other options are also used.

  r381568 added CONFIGURE_ARGS+=--with-out-mib-modules="mibII/ipv6", but the
  handling of other options can result in two different --with-out-mib-modules
  arguments being passed to configure, and only the second one has
  effect. That leads to build failures because it tries to build the old
  mibII/ipv6 which is no longer supported on freebsd.

  This change adds mibII/ipv6 to the list of excluded modules that gets turned
  into the --with-out-mib-modules argument, so it plays nice with other option
  handling.

  PR:		199401
  Approved by:	mat(mentor)
  Differential Revision:	https://reviews.freebsd.org/D5329

Changes:
  head/net-mgmt/net-snmp/Makefile
Comment 3 Ian Lepore freebsd_committer freebsd_triage 2016-02-19 23:08:18 UTC 
I stumbled across this PR while researching the problem I was having with this port, which I fixed in r409215.  I think the cause of my problem was different (using non-standard options) but the fix I did should be the fix for this PR too.