From owner-freebsd-hackers Tue Mar 12 18: 2:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id A499037B417 for ; Tue, 12 Mar 2002 18:02:34 -0800 (PST) Received: from pool0381.cvx40-bradley.dialup.earthlink.net ([216.244.43.126] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16ky63-0000d2-00; Tue, 12 Mar 2002 18:02:31 -0800 Message-ID: <3C8EB31E.19382903@mindspring.com> Date: Tue, 12 Mar 2002 18:02:06 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Craig Rodrigues Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: How to correctly detect POSIX 1003.1b features on FreeBSD? References: <20020312140904.A799@bbn.com> <3C8E742C.7C2E63B8@mindspring.com> <20020312193514.A2226@bbn.com> <20020313005940.GB32410@elvis.mu.org> <20020312201314.A2345@bbn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I told you twice already: #ifdef _POSIX_REALTIME_SIGNALS or #if defined(_POSIX_REALTIME_SIGNALS) && defined(SIGRTMIN) Isn't this covered in the reference where you are finding the definition of these functions so that you are able to even know how to call them correctly in the first place? The POSIX standard clearly covers all the feature test macros for the optional implementation parts of the standard, which includes the RT extensions. I know "bash" is incredibly broken in this regard, but saying anything bad about "bash" is fairly redundant. When (if) the feature is ever actuallysupported by FreeBSD, the manifest constant _POSIX_REALTIME_SIGNALS will be defined. If you want to support it by writing the code for FreeBSD support yourself, the Linux code is available from: http://hegel.ittc.ukans.edu/projects/posix/signals.html Be aware that you can *NOT* use the code directly, since it is GPL'ed, and will never be integrated into the FreeBSD tree if you do. You should also be aware that signal processing on FreeBSD and Linux are significantly different, and that queued signals are generally a workaround for threads or other problems, and the FreeBSD user space scheduler and signals in threads interactions are significantly more complex than those in Linux (and significantly sipler in the kernel). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message