From owner-freebsd-questions Wed Dec 24 12:09:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA27428 for questions-outgoing; Wed, 24 Dec 1997 12:09:04 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA27423 for ; Wed, 24 Dec 1997 12:09:00 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xkwuC-0005zN-00; Wed, 24 Dec 1997 11:55:48 -0800 Date: Wed, 24 Dec 1997 11:55:46 -0800 (PST) From: Tom To: Donn Miller cc: questions@freebsd.org Subject: Re: compiling glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Dec 1997, Donn Miller wrote: > First, I know that fbsd doesn't support wctype.h as a header or in it's > libc. Is it going to be incorporated info FreeBSD soon? If so, I think > that the wctype stuff from the latest glibc can be merged into the libc > from fbsd. What is wctype.h for? Header files can't be put into libraries. > Second, is there a system V compatablility package available? It would > most likely have wide-character support. Not needed. FreeBSD is system V compatible where needed. > compiling glibc -- I get errors to the effect that ENOMSG is undefined. > Are there any headers and/or libs that I can download to patch this? This > seems also to be a SYSV issue. So you are compiling glibc to get wctype.h? Installing glibc is a really good way of screwing your system up. > The reason for all this is that I was trying to compile Wine1221, and it > wanted to include , but was unavailable. Now the Wine project > people are saying something to the effect including wctype.h is wrong. > > Any suggestions or comments would be helpful. > > Donn > > > Tom