Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Dec 1997 11:55:46 -0800 (PST)
From:      Tom <tom@sdf.com>
To:        Donn Miller <dmm125@bellatlantic.net>
Cc:        questions@freebsd.org
Subject:   Re: compiling glibc
Message-ID:  <Pine.BSF.3.95q.971224115229.23016A-100000@misery.sdf.com>
In-Reply-To: <Pine.NEB.3.96.971224133550.14905A-100000@myname.my.domain>

next in thread | previous in thread | raw e-mail | index | archive | help

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 <wctype.h>, 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.971224115229.23016A-100000>