Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3EA6BF5C.AC81A9E@doe.carleton.ca> Date: Wed, 23 Apr 2003 12:29:17 -0400 From: Fred Ma X-Accept-Language: en MIME-Version: 1.0 To: Brian Ford , cygwin AT cygwin DOT com Subject: Re: Problem building ddd on cygwin References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Brian Ford wrote: > Please keep replies on the list so others can help. I apologize if I > should not have CC'ed you, but I wasn't sure you were subscribed, > especially in light of your cross post. Yes. I hope all the groups are considered relevant to the problem. It was hard to tell where the root problem and solution lies. > Cygwin keeps two versions of gcc around. Plain gcc is "gcc (GCC) 3.2 > 20020927 (prerelease)". gcc-2 is "2.95.3-10". Look in Cygwin's setup and > install the package named gcc2. I am not sure what category it is under, > though. > > > All in all, it sounds kind of sobering. Even if I > > spend the time to find out about gcc-2 and how > > to use it, I will still be battling the bugs you > > encountered. Nows about time to re-acquaint > > myself with command-line gdb. > > > Well, there is really no time involved for getting gcc-2 and using it to > compile ddd. Like I said before, I haven't spent much time at all > debugging the ddd <-> gdb interaction. I've also had weird problems with > gdb that no one else seems to have, and I have a few versions lying around > because of custom development. YMMV. > > Let me know if you find something and need help debugging. > -- > Brian Ford > Senior Realtime Software Engineer > VITAL - Visual Simulation Systems > FlightSafety International > Phone: 314-551-8460 > Fax: 314-551-8444 My urge to take swaps at building ddd on cygwin has come in phases. At first, I think it's not worth the bother. Then I get frustrated at the lack of a GUI, and give it a try. Ran into the message a few months ago, and found from web searching that I wasn't the only one. Got use to commandline again, then got frustrated again, sleuthed down the error to the extent I described, posted it, and got use to command line again. It won't be too long before I get into the phase of giving it another go. Thanks for the offer. Fred P.S. Since the solution seems specific to cygwin, I've only copied the cygwin forum. -- Fred Ma, fma AT doe DOT carleton DOT ca Carleton University, Dept. of Electronics 1125 Colonel By Drive, Ottawa, Ontario Canada, K1S 5B6 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/