Hi Junfeng
As you said followings, I took qemu_accel of Tizen:Mobile to be built just now.
[Junfeng] This is because the repository of “qemu_accel” of Tizen:Mobile isn’t build now. No binary of “cross-armv7l-gcc48…” is generated. If it gets build in Tizen:Mobile, I believe qemu-accel-armv7l will use the one from Tizen:Mobile.
Release engineer team, Please open the build of qemu_accel of Tizen:Mobile. This repository is necessary to open all the time.
I have more questions for this.
Do all packages in qemu_accel of Tizen:Mobile need to be built?
If do not, could you describe the packages which need to be built in qemu_accel of Tizen:Mobile.
I think that qemu_accel of Tizen:Mobile has disable build flag by default and some packages have enable 'Explicitly enable' option for build.
How do you think about this?
Do I need to build qemu repository in Tizen:Mobile?
I think this repository is similar with qemu_accel, right?
Thanks
Jinkun Jang
------- Original Message -------
Sender : Dong, Junfeng<[email protected]>
Date : 2013-11-05 20:16 (GMT+09:00)
Title : RE: [Dev][Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
From: 김보곤 [mailto:[email protected]]
Sent: Tuesday, November 05, 2013 6:36 PM
To: Dong, Junfeng; [email protected]
Cc: Nashif, Anas; 장진근
Subject: [Dev][Tizen 3.0] cross build environment problem because of cross-gcc and cross-qemu
Dear Junfeng.
There are two issues on cross build environment.
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.
During I try to test this one, I've also found out another problem.
I think this is related to Tizen:Mobile qemu_accel repository configuration.
Each native platform module has been built by cross toolchain installing qumu-accel-armv7l / qemu_accel / Tizen:Mobile.
When this qumu-accel-armv7l install cross-armv7l-gcc48-icecream-backend, they use Tizen project one instead of Tizen:Mobile project one.
Because of this, all our patches for cross-armv7l-gcc48-icecream-backend is not reflected.
[Junfeng] This is because the repository of “qemu_accel” of Tizen:Mobile isn’t build now. No binary of “cross-armv7l-gcc48…” is generated. If it gets build in Tizen:Mobile, I believe qemu-accel-armv7l will use the one from Tizen:Mobile.
Release engineer team, Please open the build of qemu_accel of Tizen:Mobile. This repository is necessary to open all the time.
Thanks
Junfeng
I think this two problem should be solved to fix some build failure on Tizen:Mobile.
Best regards
Bogon Kim
|
|
|
|
-----------------------------------------------------------------
Jinkun Jang
Engineer
System S/W Lab.
Software R&D Center
SAMSUNG ELECTRONICS CO., LTD.
TEL : 82-31-279-7689
MOBILE : 82-10-9210-7689
e-mail : [email protected]
-----------------------------------------------------------------
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
