Date: Fri, 15 Feb 2019 21:02:35 -0800 From: Enji Cooper <yaneurabeya@gmail.com> To: Robert Huff <roberthuff@rcn.com> Cc: current@freebsd.org Subject: Re: problem building dev/e1000 Message-ID: <77EDD0AB-BAAC-460F-B2E1-46ABA5045178@gmail.com> In-Reply-To: <23655.5954.25347.254867@jerusalem.litteratus.org> References: <23653.56460.521599.489556@jerusalem.litteratus.org> <754B5C21-656B-4A67-BA39-50BB4AF5C0CD@gmail.com> <CAKdFRZjdR0%2BMEFhApLcV5me8Nt=R7F1yOoW34owQYne-T9Ehmg@mail.gmail.com> <652F1541-52DE-4744-8AEA-8EE6434E04E8@gmail.com> <39629f6cb41cff32b348cf5d329d425352c28464.camel@freebsd.org> <0b234c9e-7799-e956-997c-c34762d57f4b@FreeBSD.org> <23655.5954.25347.254867@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 15, 2019, at 11:47, Robert Huff <roberthuff@rcn.com> wrote: >=20 > Lev Serebryakov writes: >=20 >>> My question would be: why? If some drivers have a new=20 >>> dependency on iflib, why isn't that expressed in sys/conf/files=20 >>> and handled automatically? >>=20 >> My question exactly. >=20 > I am so glad people who know what they're talking about have the > same response I did. :-) I totally missed the part where Robert said he was compiling it into the ker= nel. Also, I remember the days when drivers didn=E2=80=99t automatically com= pile in dependent options (example: =E2=80=9Cdevice re=E2=80=9D requires =E2= =80=9Cdevice miibus=E2=80=9D). I guess things have changed a bit in the past= year [while I was away] with some drivers? Thanks, -Enji >=20 > Respectcfully, >=20 >=20 > Robert Huff >=20 >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77EDD0AB-BAAC-460F-B2E1-46ABA5045178>