X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Paul Bibbings Subject: Re: Problems with qt4, requiring local repair Date: Wed, 03 Mar 2010 02:48:16 +0000 Lines: 36 Message-ID: <87d3zmruhb.fsf@gmail.com> References: <871vg37s1o DOT fsf AT gmail DOT com> <4B8C2466 DOT 3030803 AT gmail DOT com> <4B8C24FE DOT 4040300 AT gmail DOT com> <87r5o367es DOT fsf AT gmail DOT com> <4B8DB00B DOT 5070400 AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (windows-nt) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Dave Korn writes: > On 01/03/2010 21:47, Paul Bibbings wrote: >> On the current problem, having tidied up the libraries, I can get a >> basic Qt4 app to build, but I'm not getting any joy running it. It >> merely hangs at a point that I am still trying to trace through >> debugging with gdb; and this is building using the Cygwin distro >> gcc-4.3.4. > > Keep us posted; if you think there's a real bug in the compiler or related > runtime support, I'm always interested. > > cheers, > DaveK As it turned out this was not a problem with either the Qt installations nor with gcc-4. It was merely a minor problem with the configuration of my Xserver (WinX). I didn't notice this at first because the test apps that I had built with Qt4 were not outputting any errors where the same apps built with Qt3 immediately showed a "can't connect to the server" flavour error. I have managed to sort this, so no further problems to report in this regard, thankfully. On the question of how my gcc-4.4.3 installation is configured - having not disabled sjlj execeptions - I had omitted this believing that the latest versions of gcc could discover from the environment whether dw2 exceptions were available and would only use sjlj where this was found not to be the case. I'm now not sure what the detailed implications of this are for linking against cygwin distro libs, but I can say that I haven't actually encountered any problems yet. I will, however, reconfigure and rebuild, all the same. Thank you for your input and help. Regards Paul Bibbings -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple