From owner-freebsd-current Fri Oct 15 10:59:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 87768151A1 for ; Fri, 15 Oct 1999 10:59:45 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id KAA24276; Fri, 15 Oct 1999 10:59:13 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199910151759.KAA24276@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: Timeframe on XFree86 signal fix In-reply-to: Your message of "Fri, 15 Oct 1999 15:19:43 +0200." <66595.939993583@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 10:59:13 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi folks, > > A sequence of silly mistakes and circumstances have conspired against me > to make it impossible for me to run XFree86. I understand that the > XFree86 build is broken in the face of recent signal-related changes. > > I want to know how long I can expect to wait for XFree86 to build on > CURRENT again. I'm not pushing, I just want to know whether I'm in for a > wait of less than a week (in which case I'll do without XFree86) or > whether I can expect to wait longer (in which case I'll bite the bullet > and undo my silly mistakes). > I too was pressed for time and what I did was to dig up the source for a program which uses signals and cut paste the include files to FSConServ.c . I played a little with gcc -E which displays the processing of the include files and took a brief look at signa.h and saw the check for _P1003_1B_VISIBLE... This is all academic since the proper fix was posted to the list. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message