From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50317 invoked by alias); 10 Feb 2020 14:55:27 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 50309 invoked by uid 89); 10 Feb 2020 14:55:27 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*MI:sk:fb3fb6c, H*i:sk:fb3fb6c, H*f:sk:fb3fb6c, HContent-Transfer-Encoding:8bit X-HELO: mailsrv.cs.umass.edu Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Feb 2020 14:55:22 +0000 Received: from [192.168.0.21] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 2A552401CE43; Mon, 10 Feb 2020 09:55:20 -0500 (EST) Reply-To: moss@cs.umass.edu Subject: Re: Can't compile port qtermwidget To: cygwin@cygwin.com References: <4f7262ba-4257-625c-c04b-7ba6496309c4@galbraiths.ca> From: Eliot Moss Message-ID: Date: Mon, 10 Feb 2020 14:55:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00087.txt.bz2 On 2/9/2020 10:21 PM, Paul Galbraith via cygwin wrote: > On 2020-02-09 5:18 p.m., Eliot Moss wrote: >> I am not Qt savvy, but I can think of two generic things to check: >> >> - The Qt version in the cygwin libraries you have, versus what qtermwidget expects. >> >> - The version of the C compiler (gcc keeps evolving, and that sometimes breaks things). >>   Maybe there is info on the web about Qt issues with various version of gcc. > > Thanks Eliot.  The package works with the current Qt libs so I'm working under the assumption that > the Qt version is Ok. > > I've figured out that if -DQT_NO_CAST_FROM_ASCII and -DQT_NO_CAST_TO_ASCII are removed from the > compile directives, the situation improves drastically (at least on the first file I tried to > compile manually, the number of compile errors goes from dozens to zero).  But, I don't know why > Cmake is adding those directives. I wonder ... are there relevant ./configure options? EM -- 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