From owner-freebsd-current@FreeBSD.ORG Sat Feb 28 19:06:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 71EF816A4CF; Sat, 28 Feb 2004 19:06:06 -0800 (PST) In-Reply-To: <1077558726.664.3.camel@localhost.localdomain> from Ray Seals at "Feb 23, 2004 11:52:06 am" To: rseals@vdsi.net Date: Sat, 28 Feb 2004 19:06:06 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040229030606.71EF816A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@freebsd.org Subject: Re: ndiscvt line 13 syntax error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Feb 2004 03:06:06 -0000 > System is running current as of Feb. 21st 19:00 central. These are > drivers for a broadcom wireless card (built-in) on a laptop. "A" Broarcom card? "A" laptop? > # ls > Makefile bcmwl5.inf bcmwl5.sys > # ndiscvt -i bcmwl5.inf -s bcmwl5.sys -o ndis_driver_data.h > ndiscvt: line 13: e: syntax error. > __[# > > If you need any additional information let me know. It would have killed you to show us what was on line 13 in bcmwl5.inf that made the INF parser in ndiscvt(8) choke? Look people: there are a zillion different variants of Broadcom's driver software. I don't have them all. Use some common sense here: if your particular .inf file makes ndiscvt(8) unhappy, then provide me a link to the file so I can figure out why. Some .inf files are provided in unicode format. You need to run them through iconv to turn them back into ASCII. I have no idea what's the matter with this one since you didn't show me the contents. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================