Date: Sun, 31 Dec 95 22:23 WET From: uhclem@nemesis.lonestar.org (Frank Durda IV) To: rjk@watson.grauel.com, freebsd-hackers@freebsd.org Cc: uhclem@nemesis.lonestar.org Subject: An answer, a question, and an offer... Message-ID: <m0tWbmN-000BzGC@nemesis.lonestar.org>
next in thread | raw e-mail | index | archive | help
[0]First, a problem and solution with the 2.0.5 ==> 2.1 upgrade: after you've [0]done the upgrade, the GENERIC kernel won't compile due to problems with the [0]matcd driver. This is due to the fact that the 2.0.5 driver #included the [0]file `i386/isa/matcd/matcd.h', which is no longer used by the 2.1 driver [0]but is still there since the upgrade process just writes over existing [0]files; it seems that config causes it to be #included if it exists. Either [0]move it out of the way or remove it, and re-run config. This is a known problem, and it has been discussed before in -current and in the USENET freebsd groups. The solution is to delete /usr/src/sys/i386/isa/matcd/matcd.h, do a make depend and then a make. It was discovered at a date where I guess there wasn't time to have the install get rid of old files in the source tree before extracting the new tree. Doing something like this is a religious area anyway. There are other files around the entire 2.0.5 (and 2.0.0 and 1.1.5.1) system that will also be hanging around if you have upgraded over each of these instead of doing a fresh extract of the source tree, but as far as I know, the matcd.h is the only one that causes the build to fail for the 2.0.5 -> 2.1.0 jump. The rest of the "dead" files just waste space and make things messy. Frank Durda IV <uhclem@nemesis.lonestar.org>|"Mr. Bill, you claimed that you | would sell eighty-eight million ...letni!rwsys!nemesis!uhclem | billion copies of Windows '95 | in the first four months alone. Aren't you disappointed?" :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0tWbmN-000BzGC>