Date: Tue, 04 Aug 2009 15:20:20 +0400 From: Alex Zimnitsky <aavzz@yandex.ru> To: freebsd-hackers@freebsd.org Subject: Re: sys/cdefs.h not included automatically Message-ID: <1249384820.2928.22.camel@localhost.localdomain> In-Reply-To: <e71790db0908032226i4325eec8sb28586048d77a4fc@mail.gmail.com> References: <1249329403.2928.11.camel@localhost.localdomain> <e71790db0908032226i4325eec8sb28586048d77a4fc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
04/08/2009 в 02:26 -0300, Carlos A. M. dos Santos: > On Mon, Aug 3, 2009 at 4:56 PM, Alex Zimnitsky<aavzz@yandex.ru> wrote: > > Hello, freebsd-hackers > > > > my system is 7.2-RELEASE > > > > there is a <sys/cdefs.h> which is included in a lot of headers, but a > > few of them instead of including it, generate "#error this file needs > > sys/cdefs.h". > > > > seems like an omission, but if it's intentional I'm curious why it is > > so. > > Those files are not intended to be directly included by user programs. > You usually include them indirectly. See, for instance, pthread.h and > stddef.h. > OK, the reason of my asking was configure script in a 3rd party application (namely apr-1.3.6) that generated strange warning about sys/syslimits.h being good enoung for gcc but not for gcc -E. it seems, they have a bug in checking for the presence of limits.h and sys/syslimits.h and include them in a non-uniform manner later. going to send them a patch Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1249384820.2928.22.camel>