Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Lesstif compilation problem and setup.exe
Date: Mon, 11 Nov 2002 15:24:56 -0500
Message-ID: <7BFCE5F1EF28D64198522688F5449D5AD63AC1@xchangeserver2.storigen.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Scott Prive" <Scott DOT Prive AT storigen DOT com>
To: "Mark Manning" <markem AT ev1 DOT net>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id gABKnlU08305

> -----Original Message-----
> From: Mark Manning [mailto:markem AT ev1 DOT net]
> Sent: Monday, November 11, 2002 12:20 PM
> To: cygwin AT cygwin DOT com
> Subject: Lesstif compilation problem and setup.exe
> 

<snipped out your primary problem which I can't help with..>

> If you need a screen dump - let me know.  I can either try to capture 
> the text itself (didn't work before but I can try again) or 
> do a screen 
> capture (found a nice on-line product).  Didn't want to post 
> the screen 
> capture.

See `man script`. Run this before doing your compile, and you'll begin a disk log of everything on your terminal.

Even if the process dies at the same as the others, it should have a record up until that point. If it's a reasonable size for posting, the general concensus is to post as an attachment so it doesn't generate false hits in the list archive searches..

For your primary concern, hopefully someone else will step up with real answers.  :-)

You might also attempt compiling & building a smaller package to triage "what" breaks your system (ie, try packaging bash and avoiding anything X-related).



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/