I remember getting mails about my driver before, so it's ok. Basically,
whenever bsd.kmod.mk is broken, my module (being the first in the list),
is always where the error pops up. I'll take a look at it, but you shouldn't
be using it on -stable. It is only guaranteed to work on -current, in fact,
Hi Coleman,
Could you take a look at the 3dfx module build as handled under the
buildkernel target? It breaks on can't find kernel source if the /sys
symbolic link is broken. It shouldn't need that, right?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Sheldon Hearn [EMAIL PROTECTED] writes:
Hi Coleman,
Could you take a look at the 3dfx module build as handled under the
buildkernel target? It breaks on can't find kernel source if the /sys
symbolic link is broken. It shouldn't need that, right?
This isn't Coleman's fault; it's a bug
On Wed, 25 Jul 2001 03:45:34 MST, Dima Dorfman wrote:
This isn't Coleman's fault; it's a bug in bsd.kmod.mk, which was fixed
in r1.86 (or r1.75.2.3 in RELENG_4), and it affects all modules (3dfx
is failing because it's first on the list). Are you running a stale
-stable (e.g., before
