From owner-freebsd-hackers Sun Feb 1 22:16:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09657 for hackers-outgoing; Sun, 1 Feb 1998 22:16:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cam.grad.kiev.ua (grad-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09623 for ; Sun, 1 Feb 1998 22:16:32 -0800 (PST) (envelope-from Ruslan@Shevchenko.kiev.ua) Received: from Shevchenko.kiev.ua (localhost [127.0.0.1]) by cam.grad.kiev.ua (8.8.8/8.8.5) with ESMTP id KAA13463; Sun, 1 Feb 1998 10:11:57 +0200 (EET) Message-ID: <34D42E48.C62E6993@Shevchenko.kiev.ua> Date: Sun, 01 Feb 1998 10:11:54 +0200 From: Ruslan Shevchenko X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: Alex CC: hackers@FreeBSD.ORG Subject: Re: egcs and Qt? References: Content-Type: multipart/mixed; boundary="------------8661348496FE1515019398AB" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" This is a multi-part message in MIME format. --------------8661348496FE1515019398AB Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Alex wrote: > Has anyone had luck making the Qt port? I've tried the latest libg++ > (2.8.0 snapshots) in both static and shared form, to no avail. I was able > to get the Qt port to compile, but linking against the generated library > produced many many errors. However creating programs with egcs (or any > gcc) linked against the libraries created FreeBSD's gcc (2.7) seem to work > fine. Has anyone had better results with an a.out system? Any > suggestions? > > Linux: The Microsoft Windows(tm) of the Unix(tm) world. > Linux fun's probabily solve this problem ;)(look at attachment) > - alex -- @= //RSSH mailto://Ruslan@Shevchenko.Kiev.UA --------------8661348496FE1515019398AB Content-Type: text/plain; charset=x-user-defined; name="x" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="x" >From - Sun Feb 1 10:08:58 1998 Received: from nbki.ipri.kiev.ua (mails.ipri.kiev.ua [194.44.146.18]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with ESMTP id MAA21839 for ; Sun, 18 Jan 1998 12:05:57 +0200 (EET) Received: from cygnus.com (runyon.cygnus.com [205.180.230.5]) by nbki.ipri.kiev.ua (8.8.5/8.8.5) with ESMTP id MAA10112 for ; Sun, 18 Jan 1998 12:06:52 +0200 (EET) Received: (from majordom@localhost) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) id NAA15624; Fri, 16 Jan 1998 13:10:38 -0800 (PST) X-Authentication-Warning: panic.can.seawood.org: cls owned process doing -bs Date: Fri, 16 Jan 1998 13:08:50 -0800 (PST) X-UIDL: 885121530.040 From: Christopher Seawood X-Sender: cls@panic.can.seawood.org To: qt-bugs@troll.no, qt-interest@troll.no, egcs@cygnus.com Subject: Qt & gcc-2.8.0/egcs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-egcs@cygnus.com Precedence: bulk Status: U X-Mozilla-Status: 8001 I have available a patch to qt-1.31 that gets rid of the extra warning messages of gcc-2.8.0/egcs complaining about not explicitly calling the base class when declaring a copy constructor. The patch is available at http://www.seawood.org/linux/qt-1.31-gcc.patch. This also brings up a question about the qt license which everyone can feel free to ignore (ie, no flamewars, please). I had to make a patch to the base classes to fix these problems. According to the Free License, I cannot distribute an srpm with these changes nor can I distribute any rpms of qt programs I've built using my "modified" libraries. This is mildly annoying. Hypothetically speaking, if 1.31 was the last free qt release then users would have to put up with the extra warning messages and hope that the next release of gcc doesn't completely break qt. Or they would have to remember to use an old version of gcc if they want to develop qt apps. That's too much of a hassle, IMO. If the last free release of qt was made LGPL'd instead of using the qt source license, then this would not be an issue. Regards Christopher --- Christopher Seawood * Software Engineer/System Admin cls@seawood.org * http://www.seawood.org --------------8661348496FE1515019398AB--