From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14283 invoked by alias); 24 Nov 2003 18:15:09 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 14269 invoked from network); 24 Nov 2003 18:15:08 -0000 Received: from unknown (HELO sys02.mail.msu.edu) (35.9.75.102) by sources.redhat.com with SMTP; 24 Nov 2003 18:15:08 -0000 Received: from office.ixn.com ([68.23.74.57] helo=msu.edu) by sys02.mail.msu.edu with asmtp (Exim 4.10 #3) (TLSv1:RC4-MD5:128) id 1AOLEq-000Faj-00 for cygwin-xfree@cygwin.com; Mon, 24 Nov 2003 13:15:08 -0500 Message-ID: <3FC24AA6.9020708@msu.edu> Date: Mon, 24 Nov 2003 18:15:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relate d to Motif?] References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00405.txt.bz2 List-Id: Richard, Richard Campbell wrote: >>Somebody needs to take it upon themself to port DDD and make appropriate >>fixes to make it work on Cygwin/X. This has not been done to date, as >>far as I can recall, and it is likely to need to be done before ddd will >>"just work". I don't see a lot happening with DDD until someone steps >>forward to port it properly. > > > In previous versions (cygwin, xfree, ddd), DDD did compile and run out > of the box. I believe that is why no one took it upon themselves > previously. > > see http://www.cygwin.com/ml/cygwin/2003-09/msg00241.html Okay. That is good to know. However, a lot has happened since then and I stand by my point that someone will have to dedicate some time to getting this to work. The LessTif questions could be a red herring... the problem might be that there are some #ifdef __CYGWIN__'s in the code that cause problems with the new Cygwin 1.5.3-x + versions. However, it could be any number of issues. Harold