[uClibc]signal.h problem ?

Erik Andersen andersen at lineo.com
Thu Sep 6 22:47:40 UTC 2001


On Thu Sep 06, 2001 at 03:42:21PM -0700, David Schleef wrote:
> On Thu, Sep 06, 2001 at 04:58:57AM -0700, Luke wrote:
> > Hi,
> > 
> > I was trying to compile a program that used <signal.h> with uclibc and was getting a parse error
> > whereas the same code compiles fine under glibc.  I narrowed down the problem to the simplest code
> > that had the error:
> 
> It works if you add:
> 
>   #define __USE_POSIX199309
> 
> Erik, what's up with various *_SOURCE defines and what standards are
> supposed to be supported?  I'm not sure if this is a bug or design.

I'm actually working on merging glibc 2.4.4 headers, to try and
fix up some of these sorts of issues (as well as making it easier
to make C++ go).  I've got the headers all merged, and I'm just
fixing up the last wierd problems.  This should make these sorts
of things be much better behaved.

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--





More information about the uClibc mailing list