From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id 1441D601D6 for ; Tue, 25 Jun 2013 09:33:17 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r5P9XFbf018139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 25 Jun 2013 02:33:15 -0700 (PDT) Received: from [128.224.162.205] (128.224.162.205) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.2.342.3; Tue, 25 Jun 2013 02:33:14 -0700 Message-ID: <51C963C0.5020009@windriver.com> Date: Tue, 25 Jun 2013 17:32:48 +0800 From: Kang Kai User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: oe-core X-Originating-IP: [128.224.162.205] Cc: Paul Eggleton Subject: Could qt4.8 build on mips 64 bits platform? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 09:33:17 -0000 Content-Type: multipart/alternative; boundary="------------090705040201090806020904" --------------090705040201090806020904 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Hi All, Could qt4.8 build on mips 64 bits platform? I searched qt-project.org and no such related information. And then grep the source codethat no such mips64 keyword in file qmake.conf under directory mkspecs. In contrast there are mips32 related flags in mkspecs/qws/linux-mips-g++/qmake.conf. Does that mean we still can't build qt 4.8 on mips64? Thanks a lot. -- Regards, Neil | Kai Kang --------------090705040201090806020904 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit Hi All,

Could qt4.8 build on mips 64 bits platform?

I searched qt-project.org and no such related information.
And then grep the source code that no such mips64 keyword in file qmake.conf under directory mkspecs. In contrast there are mips32 related flags in mkspecs/qws/linux-mips-g++/qmake.conf.

Does that mean we still can't build qt 4.8 on mips64?

Thanks a lot.

-- 
Regards,
Neil | Kai Kang

--------------090705040201090806020904-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mail.openembedded.org (Postfix) with ESMTP id D59C260780 for ; Tue, 25 Jun 2013 10:41:37 +0000 (UTC) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 25 Jun 2013 03:39:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,936,1363158000"; d="scan'208";a="335170507" Received: from unknown (HELO helios.localnet) ([10.252.122.97]) by orsmga001.jf.intel.com with ESMTP; 25 Jun 2013 03:41:37 -0700 From: Paul Eggleton To: Kang Kai Date: Tue, 25 Jun 2013 11:41:36 +0100 Message-ID: <1810438.1YW5iENKFC@helios> Organization: Intel Corporation User-Agent: KMail/4.10.3 (Linux/3.8.0-25-generic; KDE/4.10.3; i686; ; ) In-Reply-To: <51C963C0.5020009@windriver.com> References: <51C963C0.5020009@windriver.com> MIME-Version: 1.0 Cc: oe-core Subject: Re: Could qt4.8 build on mips 64 bits platform? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 10:41:37 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Tuesday 25 June 2013 17:32:48 Kang Kai wrote: > Could qt4.8 build on mips 64 bits platform? > > I searched qt-project.org and no such related information. > And then grep the source codethat no such mips64 keyword in file > qmake.conf under directory mkspecs. In contrast there are mips32 related > flags in mkspecs/qws/linux-mips-g++/qmake.conf. > > Does that mean we still can't build qt 4.8 on mips64? I don't have any specific knowledge here; I'd suggest trying it. If additional patches are needed the best thing would be to try and get those merged upstream. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id E36EF6007C for ; Thu, 27 Jun 2013 14:11:01 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r5REB1i1009317 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 27 Jun 2013 07:11:01 -0700 (PDT) Received: from [128.224.162.205] (128.224.162.205) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 27 Jun 2013 07:10:59 -0700 Message-ID: <51CC47DA.8090905@windriver.com> Date: Thu, 27 Jun 2013 22:10:34 +0800 From: Kang Kai User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Paul Eggleton References: <51C963C0.5020009@windriver.com> <1810438.1YW5iENKFC@helios> In-Reply-To: <1810438.1YW5iENKFC@helios> X-Originating-IP: [128.224.162.205] Cc: oe-core Subject: Re: Could qt4.8 build on mips 64 bits platform? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 14:11:02 -0000 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit On 2013年06月25日 18:41, Paul Eggleton wrote: > On Tuesday 25 June 2013 17:32:48 Kang Kai wrote: >> Could qt4.8 build on mips 64 bits platform? >> >> I searched qt-project.org and no such related information. >> And then grep the source codethat no such mips64 keyword in file >> qmake.conf under directory mkspecs. In contrast there are mips32 related >> flags in mkspecs/qws/linux-mips-g++/qmake.conf. >> >> Does that mean we still can't build qt 4.8 on mips64? > I don't have any specific knowledge here; I'd suggest trying it. If additional > patches are needed the best thing would be to try and get those merged > upstream. Thanks a lot. I'll try to build it on mips 64. Regards, Kai > > Cheers, > Paul > -- Regards, Neil | Kai Kang From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mail.openembedded.org (Postfix) with ESMTP id DF88A6A8D1 for ; Thu, 27 Jun 2013 16:35:48 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r5RGZjob027703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 27 Jun 2013 09:35:46 -0700 (PDT) Received: from [128.224.147.234] (128.224.147.234) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.342.3; Thu, 27 Jun 2013 09:35:45 -0700 Message-ID: <51CC69DA.3010406@windriver.com> Date: Thu, 27 Jun 2013 12:35:38 -0400 From: Randy MacLeod User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Kang Kai References: <51C963C0.5020009@windriver.com> <1810438.1YW5iENKFC@helios> <51CC47DA.8090905@windriver.com> In-Reply-To: <51CC47DA.8090905@windriver.com> X-Originating-IP: [128.224.147.234] Cc: Paul Eggleton , oe-core Subject: Re: Could qt4.8 build on mips 64 bits platform? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 16:35:49 -0000 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit On 13-06-27 10:10 AM, Kang Kai wrote: > On 2013年06月25日 18:41, Paul Eggleton wrote: >> On Tuesday 25 June 2013 17:32:48 Kang Kai wrote: >>> Could qt4.8 build on mips 64 bits platform? >>> >>> I searched qt-project.org and no such related information. >>> And then grep the source codethat no such mips64 keyword in file >>> qmake.conf under directory mkspecs. In contrast there are mips32 related >>> flags in mkspecs/qws/linux-mips-g++/qmake.conf. >>> >>> Does that mean we still can't build qt 4.8 on mips64? >> I don't have any specific knowledge here; I'd suggest trying it. If >> additional >> patches are needed the best thing would be to try and get those merged >> upstream. > > Thanks a lot. I'll try to build it on mips 64. The background here is that we encountered many painful build problems with qt-4.7 on mips64 in oe-core-1.2. We tried to fix them initially but investigations from 6 months ago indicated that the qt upstream did not support mips64. Kai will dig into the current situation but I expect that little will have changed. We ended up with horrid bbapends such as: --- #Valid for all arches except mips64 with 64bit userspace # mips64 with n32 has host: mips64-wrs-linux-gnun32 # mips64 with n64 has host: mips64-wrsmllib64-linux # qemumips has host: mips-wrs-linux # qemumips-64 has host: mips64-wrs-linux COMPATIBLE_HOST = '((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)' --- so we'll likely need a clue on how to declare a host as incompatible or introduce an INCOMPATIBLE_HOST variable. // Randy > > Regards, > Kai > >> >> Cheers, >> Paul >> > > -- # Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mail.openembedded.org (Postfix) with ESMTP id B2C866ABBF for ; Thu, 27 Jun 2013 16:47:38 +0000 (UTC) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r5RGrx1J027314; Thu, 27 Jun 2013 17:53:59 +0100 X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9JQjyvTr9r6x; Thu, 27 Jun 2013 17:53:58 +0100 (BST) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r5RGrtxs027310 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 27 Jun 2013 17:53:56 +0100 Message-ID: <1372351613.9930.225.camel@ted> From: Richard Purdie To: Randy MacLeod Date: Thu, 27 Jun 2013 17:46:53 +0100 In-Reply-To: <51CC69DA.3010406@windriver.com> References: <51C963C0.5020009@windriver.com> <1810438.1YW5iENKFC@helios> <51CC47DA.8090905@windriver.com> <51CC69DA.3010406@windriver.com> X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Cc: Paul Eggleton , oe-core Subject: Re: Could qt4.8 build on mips 64 bits platform? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 16:47:39 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2013-06-27 at 12:35 -0400, Randy MacLeod wrote: > We ended up with horrid bbapends such as: > --- > #Valid for all arches except mips64 with 64bit userspace > # mips64 with n32 has host: mips64-wrs-linux-gnun32 > # mips64 with n64 has host: mips64-wrsmllib64-linux > # qemumips has host: mips-wrs-linux > # qemumips-64 has host: mips64-wrs-linux > COMPATIBLE_HOST = > '((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)' > --- > > so we'll likely need a clue on how to declare a host as incompatible > or introduce an INCOMPATIBLE_HOST variable. I suspect something like this should work: COMPATIBLE_HOST_mips64 = "" Cheers, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mail.openembedded.org (Postfix) with ESMTP id 5E10A60780 for ; Fri, 28 Jun 2013 02:53:06 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r5S2r4C8020626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 27 Jun 2013 19:53:04 -0700 (PDT) Received: from [128.224.162.205] (128.224.162.205) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 27 Jun 2013 19:53:04 -0700 Message-ID: <51CCFA77.4080506@windriver.com> Date: Fri, 28 Jun 2013 10:52:39 +0800 From: Kang Kai User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Richard Purdie References: <51C963C0.5020009@windriver.com> <1810438.1YW5iENKFC@helios> <51CC47DA.8090905@windriver.com> <51CC69DA.3010406@windriver.com> <1372351613.9930.225.camel@ted> In-Reply-To: <1372351613.9930.225.camel@ted> X-Originating-IP: [128.224.162.205] Cc: Paul Eggleton , oe-core Subject: Re: Could qt4.8 build on mips 64 bits platform? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 02:53:06 -0000 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit On 2013年06月28日 00:46, Richard Purdie wrote: > On Thu, 2013-06-27 at 12:35 -0400, Randy MacLeod wrote: >> We ended up with horrid bbapends such as: >> --- >> #Valid for all arches except mips64 with 64bit userspace >> # mips64 with n32 has host: mips64-wrs-linux-gnun32 >> # mips64 with n64 has host: mips64-wrsmllib64-linux >> # qemumips has host: mips-wrs-linux >> # qemumips-64 has host: mips64-wrs-linux >> COMPATIBLE_HOST = >> '((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)' >> --- >> >> so we'll likely need a clue on how to declare a host as incompatible >> or introduce an INCOMPATIBLE_HOST variable. > I suspect something like this should work: > > COMPATIBLE_HOST_mips64 = "" Thanks. We still need include such packages on mips64 with 32 bits filesystem. So the following is needed: COMPATIBLE_HOST_mips64 = "mips64.*-linux-gnun32" I am little worried that "-gnun32" is a standard name then I'll figure it out. Regards, Kai > > Cheers, > > Richard > > -- Regards, Neil | Kai Kang