I've finished to change the sysroot.
https://review.tizen.org/gerrit/#/c/12356/
When I change the sysroot, c++ include path cannot be found.
So I change the c++ include path as well which can be identifed automatically by cross-gcc driver.
https://review.tizen.org/gerrit/#/c/12354/
And I also add the gcc bug patch which doesn't identify the properly when sysroot is "root".
https://review.tizen.org/gerrit/#/c/12350/
It has been verified below one.
https://build.tizen.org/project/show?project=devel%3Aarm_toolchain%3AMobile
BRs
Bogon Kim
------- Original Message -------
Sender : Dong, Junfeng<[email protected]>
Date : 2013-11-06 14:38 (GMT+09:00)
Title : RE: RE: RE: [Dev][Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
First, you miss the package “qemu_aggregate”, which is used to ship “qemu-accel-armv7l” from repository “qemu-accel” to repository “arm”. I added it.
Then you can trigger a rebuild via website. For example, apps.CertificateSelector
on the above url, click “arm” on right side of web page under “Build results” column. Then you can see the “Tigger Build” button.
now you can see the package fail to build because compiler doesn’t work.
Junfeng
From: 김보곤 [mailto:[email protected]]
Sent: Wednesday, November 06, 2013 1:14 PM
To: Dong, Junfeng; 김보곤; [email protected]
Cc: Nashif, Anas; 장진근
Subject: Re: RE: RE: [Dev][Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
------- Original Message -------
Sender : Dong, Junfeng<[email protected]>
Date : 2013-11-06 12:56 (GMT+09:00)
Title : RE: RE: [Dev][Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
First one is gcc issue.
For the cross-armv7l-gcc48-icecream-backend, the with-sysroot and with-build-sysroot option value has to be changed.
Because of this bug, apps.CertificateSelector and osp-widget-service is failed.
After I submit below patch I will back out what I did submit some workaround patch for osp-widget-service.
I've modified gcc spec file like below.
https://review.tizen.org/gerrit/#/c/11811/
[Junfeng] Have you test all packages with this fix? we need to be cautious for such critical change.
[Bogon] I cannot because my change have a dependency with below qemu_accel problem.
If the release team help me out how to solve below problem, I will locally verify it using the staging server.
The current status is I try to build qemu-accel-armv7l, it is unresolve because I assmue there is no x86 64bit repository in the Tizen:Mobile.
And I've confirmed that the x86_64 repos are created in Tizen:Mobile. when the build is finished I will try to test again.
Bogon, Let’s test on the server first, so all of us can see the problem, if there is. I will upload the change into home:Junfeng, it takes more than one day to do a thorough build. Will give you update once it is finished or problem found.
[Bogon] Junfeng, I've already working on the subproject ofjinkun's home project.
https://build.tizen.org/project/monitor?project=home%3Ajang798%3Abuildfail
I have fixed cross-gcc and qemu-accel-armv7l.
I want to use qemu-accel-armv7l in the home projectwhen I build apps.CertificateSelector.
But I'm not good at the meta script suca as rebuild,linkbuild or block means in the OBS build system.
I added you as a maintainer of this.
Could you help me out how?
And BTW currently I am using devel:toolchain for testing gcc 4.8.2. I copied gcc48 from devel:arm_toolchain:Mobile. And fixed one problem that cross spec file lack “patch sections”.
And x86_64 repository is in http://download.tizen.org/live/Tizen:/Mobile/qemu_accel/,
Thanks
Junfeng
|
|
|
|
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
