Dear Anuj,
web-ui-fw is also failed in the Tizen:Mobile:build.
So I think the failure is not caused by my patch.
Since the staging project has been made by Jinkun,
he would know better about this situation.
I've already got +2 review points for 2 gcc patches.
And I will merge it and send SR all 3 patches when
I get +2 reviewed by other people for qemu-accel.
BRs
Bogon Kim
------- Original Message -------
Sender : ANUJ MISHRA<[email protected]> S5/Senior Engineer/Service Platform Group/Samsung Electronics
Date : 2013-11-14 16:39 (GMT+09:00)
Title : Re: Re: [Dev] [Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
Dear Bogon,
Thanks for you changes. When are you planning to raise the SR for the below changes?
Also, in below OBS url I see one new package web-ui-fw in failed list. Originally it is not failing in Tizen:Mobile project.
Could it be because of these changes or it is synching issue?
Dear Junfreng,
Also, I see you have +2 to only one of these review. What about other two reviews?
https://review.tizen.org/gerrit/#/c/12354/
https://review.tizen.org/gerrit/#/c/12350/
BR,
Anuj
------- Original Message -------
Sender : Dong, Junfeng
Date : Nov 14, 2013 16:26 (GMT+09:00)
Title : Re: [Dev] [Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
Great job!
Thanks
Junfeng
From: 김보곤 [mailto:[email protected]]
Sent: Thursday, November 14, 2013 3:00 PM
To: Dong, Junfeng; 김보곤; [email protected]
Cc: Nashif, Anas; 장진근
Subject: Re: RE: RE: RE: [Dev][Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
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
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
https://build.tizen.org/package/show?package=apps.CertificateSelector&project=home%3Ajang798%3Abuildfail
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
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
源?蹂?怨?amp;nbsp;(Bogon Kim)
Mobile Communication Division
Samsung Electronics.Co.,LTD
Mobile 82 - 10 - 3583 - 0881
E-mail [email protected]
Passion is my life
김보곤 선임(Bogon Kim)
Mobile Communication Division
Samsung Electronics.Co.,LTD
Mobile 82 - 10 - 3583 - 0881
E-mail [email protected]
Software, System and Samsung
|
|
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
