public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Kantacki <kantacki@o2.pl> To: cygwin-xfree@cygwin.com Subject: Re: libqt3-devel uic.exe segmentation fault Date: Tue, 01 May 2012 07:41:00 -0000 [thread overview] Message-ID: <4F9F9378.505@o2.pl> (raw) In-Reply-To: <4F9F4708.7050402@users.sourceforge.net> W dniu 2012-05-01 04:14, Yaakov (Cygwin/X) pisze: > On 2012-04-30 09:44, Kantacki wrote: >> I have problems with uic.exe compiler which is included to libqt3-devel >> package. > > First off, are you *absolutely* certain you want to be using qt3 and > not qt4? Qt3 is obsolete and no longer supported upstream. > I need to use gt3 library because I have program which works only with this library and the program does not want to work with qt4, so it is much easier to compile over qt3 then rewrite the program which I am not an author. >> When I run it with or without parameters I always get segmentation fault >> message. > > It probably needs to be rebuilt with gcc-4.5, but unless you can > convince me of a *really* good reason to keep it, I'll be removing it > from the distro soon. I think that backward compatibility is the main reason for keeping old version of libraries. Imagine operating system which requires rewriting of all old applications because of changed system api. In that case everything will fall apart and people will use many different and old operating system versions. Backward compatibility is always good idea. Kantacki -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2012-05-01 7:41 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-30 14:44 Kantacki 2012-05-01 2:14 ` Yaakov (Cygwin/X) 2012-05-01 7:41 ` Kantacki [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4F9F9378.505@o2.pl \ --to=kantacki@o2.pl \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).