Subject: kern/18500: sys/dev/ir/irframe.c does not compile with only TTY attachment
To: None <gnats-bugs@gnats.netbsd.org>
From: None <kre@munnari.OZ.AU>
List: netbsd-bugs
Date: 10/02/2002 17:41:36
>Number: 18500
>Category: kern
>Synopsis: sys/dev/ir/irframe.c does not compile with only TTY attachment
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Oct 02 03:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Robert Elz
>Release: NetBSD 1.6I (current as of now - 2002-10-02)
>Organization:
Prince of Songkla University
>Environment:
System: NetBSD delta.cs.mu.OZ.AU 1.5ZC NetBSD 1.5ZC (DELTA) #4: Mon May 27 23:17:55 ICT 2002 kre@delta.cs.mu.OZ.AU:/usr/src/sys.X/arch/i386/compile/DELTA i386
That described the system running send-pr, and is otherwise irrlevant.
Architecture: i386
Machine: i386
>Description:
If irframe is included, with no usb (etc) attachments,
no NIRFRAME == 0 (from config in irframe.h) then lines
87,88,89 of sys/dev/ir/irframe.c will be compiled.
Since the changes to struct cfdevice the initialisation
here is no longer correct, and the compilation fails.
>How-To-Repeat:
Compile in irframe with no irframe (specific) devices
>Fix:
Workaround is to not compile in irfrape (pseudo-dev).
Should be easy to fix for osmeone who understands the
new cfdevice struct form. I just added "{ NULL }. "
to the beginning of the initialisation, which made it
compile, but I haven't yet tested to see if that works.
>Release-Note:
>Audit-Trail:
>Unformatted: