From owner-freebsd-bugs Sun Aug 1 21:30:22 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E671A14BEF for ; Sun, 1 Aug 1999 21:30:19 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA80736; Sun, 1 Aug 1999 21:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sun, 1 Aug 1999 21:30:02 -0700 (PDT) Message-Id: <199908020430.VAA80736@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jason Young Subject: Re: kern/11891: typo in ioconf.c Reply-To: Jason Young Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/11891; it has been noted by GNATS. From: Jason Young To: freebsd-gnats-submit@freebsd.org, deuerl@indra.de Cc: Subject: Re: kern/11891: typo in ioconf.c Date: Sun, 01 Aug 1999 23:23:14 -0500 This isn't reproduceable from 3.2-RELEASE or 4.0-CURRENT (as of 7/30/99) building the GENERIC kernel which contains ex0. I can't find any mailing list traffic on current, stable, questions or bugs about it. I don't have a 3.2-STABLE box but the problem would break the GENERIC build and by extension break snapshot building, and snaps are appearing nicely on releng22.freebsd.org. ioconf.c can't really have typos in it because it's machine generated, but it could be a typo in a related file used for its generation. This commit might have something to do with the problem observed: --- 1.220.2.4 Sat May 15 18:13:57 1999 UTC by obrien Branch: RELENG_3 Diffs to 1.220.2.3 ; Diffs to 1.242 MFC: add `xe', the Xircom PC Card Ethernet driver --- Perhaps Robert cvsupped while parts of the xe support was still being installed, or needed to make depend in his build directory, or something similar. Hard to say at this point. Unless he has something else to say about it, this PR should likely be closed out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message