Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by krbdev.mit.edu (8.9.3p2) with ESMTP id PAA27701; Fri, 1 Dec 2006 15:28:10 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id kB1KS93C001551 for ; Fri, 1 Dec 2006 15:28:09 -0500 (EST) Received: from cathode-dark-space.mit.edu (CATHODE-DARK-SPACE.MIT.EDU [18.18.1.96]) (authenticated bits=56) (User authenticated as tlyu@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id kB1KS8kq022877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 1 Dec 2006 15:28:09 -0500 (EST) Received: (from tlyu@localhost) by cathode-dark-space.mit.edu (8.12.9) id kB1KS8Po004169; Fri, 1 Dec 2006 15:28:08 -0500 (EST) To: rt@krbdev.mit.edu Subject: Re: [krbdev.mit.edu #4108] Problems with 1.5 on Solaris 9 w gcc References: From: Tom Yu Date: Fri, 01 Dec 2006 15:28:08 -0500 In-Reply-To: (Henry B. Hotz's message of "Fri, 1 Dec 2006 15:20:08 -0500 (EST)") Message-Id: Lines: 24 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Scanned-BY: MIMEDefang 2.42 X-Spam-Flag: NO X-Spam-Score: 0.00 RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 1006 >>>>> "Henry" == \"\"Henry B Hotz\" via RT\" writes: Henry> On Dec 1, 2006, at 9:27 AM, Tom Yu via RT wrote: >> This sounds like an old problem with the Solaris 9 pty driver. Do you >> have patch 117171-11 (or later rev of that patch) applied? Is >> PRICNTL_HACK=1 in the arguments to runtest when you run "make check"? Henry> I have patch 117171-17 installed. (Also -07, and a patch which Henry> obsoletes -10, not that they matter.) Ok, that patch should have fixed the pty problem, and has in our experience here, so something different might be going on. Henry> I don't have a record handy, but I'm pretty sure I didn't give "make Henry> check" any special arguments to cause that. I suppose you'd like to Henry> recheck this, right? PRIOCNTL_HACK is set by the Makefile when "make check" is run in tests/dejagnu, based on whether configure detects the patch 117171-11 or later. Is the "make check" failure consistent between runs? Do you have the dbg.log file saved? ---Tom