Date: Fri, 15 Feb 2019 10:53:35 -0800 From: Enji Cooper <yaneurabeya@gmail.com> To: Eric Joyner <erj@freebsd.org> Cc: Robert Huff <roberthuff@rcn.com>, current@freebsd.org Subject: Re: problem building dev/e1000 Message-ID: <652F1541-52DE-4744-8AEA-8EE6434E04E8@gmail.com> In-Reply-To: <CAKdFRZjdR0%2BMEFhApLcV5me8Nt=R7F1yOoW34owQYne-T9Ehmg@mail.gmail.com> References: <23653.56460.521599.489556@jerusalem.litteratus.org> <754B5C21-656B-4A67-BA39-50BB4AF5C0CD@gmail.com> <CAKdFRZjdR0%2BMEFhApLcV5me8Nt=R7F1yOoW34owQYne-T9Ehmg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 15, 2019, at 10:46, Eric Joyner <erj@freebsd.org> wrote: > > ifdi_if.h is a system generated interface file that network drivers that depend on iflib use. It's generated from ifdi_if.m in sys/net. > > My guess is that you don't have "device iflib" defined in your kernel configuration. em(4) depends on iflib in FreeBSD 12/13, and with r343617, iflib is now explicitly a module that needs to be included in your kernel config if you want to use a driver that depends on it. It's already in the GENERIC kernel for amd64; are you using a kernel config file that doesn't inherit from GENERIC? HO Eric! iflib was a recently added requirement on stable/12 IIRC..? Does the manpage note this dependency, and is there an UPDATING entry for this change? Thanks! -Enji
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?652F1541-52DE-4744-8AEA-8EE6434E04E8>