From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 4 11:37:01 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFBCB1065704 for ; Tue, 4 Aug 2009 11:37:01 +0000 (UTC) (envelope-from aavzz@yandex.ru) Received: from forward3.yandex.ru (forward3.yandex.ru [77.88.46.8]) by mx1.freebsd.org (Postfix) with ESMTP id 771558FC0A for ; Tue, 4 Aug 2009 11:37:01 +0000 (UTC) (envelope-from aavzz@yandex.ru) Received: from smtp4.yandex.ru (smtp4.yandex.ru [77.88.46.104]) by forward3.yandex.ru (Yandex) with ESMTP id 962BB119102D for ; Tue, 4 Aug 2009 15:36:59 +0400 (MSD) Received: from [192.168.1.2] (ppp92-100-96-20.pppoe.avangarddsl.ru [92.100.96.20]) by smtp4.yandex.ru (Yandex) with ESMTPA id 58A7DD300E7 for ; Tue, 4 Aug 2009 15:36:59 +0400 (MSD) From: Alex Zimnitsky To: freebsd-hackers@freebsd.org In-Reply-To: References: <1249329403.2928.11.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8 Date: Tue, 04 Aug 2009 15:20:20 +0400 Message-Id: <1249384820.2928.22.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 8bit X-Yandex-TimeMark: 1249385819 X-Yandex-Spam: 1 X-Yandex-Front: smtp4.yandex.ru Subject: Re: sys/cdefs.h not included automatically X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 11:37:02 -0000 04/08/2009 в 02:26 -0300, Carlos A. M. dos Santos: > On Mon, Aug 3, 2009 at 4:56 PM, Alex Zimnitsky wrote: > > Hello, freebsd-hackers > > > > my system is 7.2-RELEASE > > > > there is a 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