Tizen 3.0 arm package build ====================== In Tizen 3.0, repo qemu has been used from the beginning, and the qemu in remote repo is 64 bit, so it does not work on 32bit system.
There's an easy way to use host qemu, like what we have in Tizen 2.1/2.2: 1) download latest build conf $ curl http://download.tizen.org/snapshots/tizen/rd-pq/latest/builddata/79e0766dd3434ea61584d48d343dd458fffbf065dfd393f5d3396855a7b66654-build.conf -o ~/tizen_3.0_mobile.conf 2) remove qemu related lines $ sed -i '/qemu/d' ~/ tizen_3.0_mobile.conf 3) add customized build conf to .gbs.conf $ cat ~/.gbs.conf .... [profile.xxx] buildconf = ~/tizen_3.0_mobile.conf ..... 4) build again $ gbs build ... or $ gbs build -D ~/Tizen_3.0_mobile.conf Please use the above way during your work. At the same time, we have worked out a solution to make Tizen 3.0 buildable on 32bit & 64 bit. It may take 2 ~3 days testing. Thanks for this inconvenient. Thanks Qiang -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of wk94.kim Sent: Monday, October 28, 2013 4:17 PM To: Kanevskiy, Alexander; [email protected] Cc: [email protected] Subject: Re: [Dev] Dependency on qemu package for arm build Sasha, All of our engineers uses 32 bit machine for development. It's serious problem now. I think we have to roll back this change. Thanks, Michael Kim. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kanevskiy, Alexander Sent: Monday, October 28, 2013 4:49 PM To: <[email protected]> Cc: [email protected] Subject: Re: [Dev] Dependency on qemu package for arm build Anuj, Please try to set vm.mmap_min_addr=0 and see if it help a bit. In general, it's known that qemu on 32 bit systems would misbehave randomly in case of shortage of RAM and potentially due to other combinations of libraries that it tries to run. We had discussed that topic some time ago in the mailing list, mentioning that unless those issues fixed by someone who knows arm and qemu well, it would be no way to support 32 bit systems. br, Alexander (mobile) > On 28 Oct 2013, at 03:53, "ANUJ MISHRA" <[email protected]> wrote: > > Sasha, > I've tested local build in 2 - 3 engineer's PC and everywhere it is > same issue we are getting. After 'Segmentation Fault' message build halts. It seems there still some issue with qemu may be with postinstall script. > As per your question, I will put details here > > Distro: Ubuntu 12.04 LTS 32 bit > Kernel: 3.5.0-42-generic > GBS: 0.18.1 > vm.mmap_min_addr = 65536 > > > ------- Original Message ------- > Sender : Kanevskiy, Alexander<[email protected]> > Date : Oct 28, 2013 07:59 (GMT+09:00) > Title : Re: [Dev] Dependency on qemu package for arm build > > On 27/10/13 07:33 , "ANUJ MISHRA" wrote: > > Anuj, > > are you trying to build package on 32 bit machine or 64 bit machine ? > What distro & kernel you¹re using ? > Also, can you show what would be ouput of "sysctl vm.mmap_min_addr² on > your system ? > > >> I checked the building of successful as well as failed packages locally. >> The problem that I reported before is gone but there is another crash >> I got and it is also related to qemu. I have checked extensively and >> tried to perform all possible options. It seems there is still issue >> with qemu, that needs to be resolved for local build. >> >> Here is the log: >> >> [ 36s] running qemu-accel-armv7l-cross-arm postinstall script >> [ 36s] qemu: Unsupported syscall: 202 >> [ 36s] Unable to reserve 0xf7000000 bytes of virtual address space for >> use as guest address space (check your virtual memory ulimit setting >> or reserve less using -R option) >> [ 36s] running setup postinstall script >> [ 36s] qemu: Unsupported syscall: 202 >> [ 36s] Unable to reserve 0xf7000000 bytes of virtual address space for >> use as guest address space (check your virtual memory ulimit setting >> or reserve less using -R option) >> [ 36s] initializing rpm db... >> [ 36s] qemu: Unsupported syscall: 202 >> [ 36s] qemu: Unsupported syscall: 202 >> [ 36s] qemu: uncaught target signal 11 (Segmentation fault) - core >> dumped >> [ 36s] /usr/lib/build/init_buildsystem: line 278: 903 Segmentation >> fault (core dumped) chroot $BUILD_ROOT /usr/bin/rpmdb --initdb >> >> One we receive this Segmentation fault build stopped with >> error: *** Error Summary *** >> === the following packages failed to build due to rpmbuild issue (1) >> === >> cert-svc-tizen.public-armv7l: >> /home/anujmishra/GBS-ROOT/local/repos/tizen.public/armv7l/logs/fail/c >> ert-s >> vc-1.0.1-31/log >> >> error: rpmbuild fails >> >> >> >> >> ------- Original Message ------- >> Sender : ANUJ MISHRA S5/Senior Engineer/Service Platform >> Group/Samsung Electronics Date : Oct 26, 2013 19:25 (GMT+09:00) Title >> : Re: [Dev] Dependency on qemu package for arm build >> >> Thans for update BingWei. >> I will test local build and update you. >> >> >> Anuj >> >> >> ---Original Message--- >> Sender : Liu, Bing Wei/[email protected] Date : 2013/10/26 10:40 >> (GMT+09:00) Subject : RE: [Dev] Dependency on qemu package for arm >> build >> >> Praj has deployed the qemu fix. Please give a try. >> - Bingwei >> >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Dong, Junfeng >> Sent: Friday, October 25, 2013 10:46 AM >> To: [email protected]; [email protected] >> Subject: Re: [Dev] Dependency on qemu package for arm build >> >> I filed https://bugs.tizen.org/jira/browse/TINF-317 to track the issue. >> Free feel to give comments there. >> Thanks >> Junfeng >> >> From: [email protected] >> [mailto:[email protected]] On Behalf Of ANUJ MISHRA >> Sent: Friday, October 25, 2013 10:39 AM >> To: [email protected] >> Subject: Re: [Dev] Dependency on qemu package for arm build >> >> Is that qemu issue resolved? I just checked building >> osp-web/net-config and still the local build gets stopped due to >> missing qemu package in server >> --------------------------------------------------------------------- >> ----- >> -------------------------------------------- >> info: package dependency resolving ... >> error: *** Error Summary *** >> === the following packages failed to build due to missing build >> dependencies (1) === >> osp-web: >> nothing provides qemu-linux-user >> nothing provides qemu-accel-armv7l >> >> error: rpmbuild fails >> --------------------------------------------------------------------- >> ----- >> -------------------------------------------- >> This is my snapshot url: >> http://download.tizen.org/snapshots/tizen/rd-pq/latest/ >> >> Meanwhile I observed some log message from failed packages(osp-web) >> regarding qemu in OBS. Not sure whether this is is error or not >> >> [ 234s] removing nis flags from //etc/nsswitch.conf... >> [ 234s] now finalizing build dir... >> [ 234s] qemu: Unsupported syscall: 311 >> >> >> Thanks >> >> ------- Original Message ------- >> Sender : Kanevskiy, Alexander >> Date : Oct 24, 2013 23:46 (GMT+09:00) Title : Re: [Dev] Dependency on >> qemu package for arm build >> >> On 10/24/13 17:37 , "ANUJ MISHRA" > wrote: >> >> I checked with 3~4 packages in local build and it stopped while >> resolving dependency through server for qemu. I am using RD-PQ >> snapshot. Even other Samsung engineers asking about this build >> dependency as they are solving build issue. >> >> This we did not observe in OBS. >> >> ah. ok. I had a fear that it also seen somewhere in OBS side. >> >> well, this supposed to be resolved tonight then Praj will propogate >> changes from devel:bootstrap to Tizen:Mobile. >> >> >> >> Anuj >> >> >> >> >> ---Original Message--- >> Sender : Kanevskiy, Alexander/[email protected] >> Date : 2013/10/24 20:48 (GMT+09:00) >> Subject : Re: [Dev] Dependency on qemu package for arm build Anuj, is >> it only for local build ? >> >> br, Alexander (mobile) >> >>> On 24 Oct 2013, at 13:28, "ANUJ MISHRA" > wrote: >>> >>> For arm build almost all packages inheriting qemu dependency and it >>> stop to build when it does not find these two qemu packages. >>> nothing provides qemu-linux-user >>> nothing provides qemu-accel-armv7l >>> >>> To overcome this Jerry enabled the qemu but it is unresolvable due >>> to SDL package missing. We verified that for RSA arm build qemu >>> package is integral part of it. So, disabling the qemu from build is >>> not solution but we have to resolve this package. >>> No developer able to use RD-PQ latest or near latest snapshots for >>> their local build verification. This is blocking issue to solve >>> remaining build issue in Tizen 3.0. >>> >>> There is no meaning to use another snapshots for checking local build. >>> I request qemu maintainers to resolve this package and examine its >>> dependency on SDL package quickly. Without this progress would be >>> very difficult. >>> >>> -- Anuj >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> https://lists.tizen.org/listinfo/dev >> --------------------------------------------------------------------- >> Intel Finland Oy >> Registered Address: PL 281, 00181 Helsinki Business Identity Code: >> 0357606 - 4 Domiciled in Helsinki >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution >> by others is strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all copies. >> >> >> >> >> -- >> Best regards, Alexander Kanevskiy. >> --------------------------------------------------------------------- >> Intel Finland Oy >> Registered Address: PL 281, 00181 Helsinki Business Identity Code: >> 0357606 - 4 Domiciled in Helsinki >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution >> by others is strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all copies. >> _______________________________________________ >> Dev mailing list >> [email protected] >> https://lists.tizen.org/listinfo/dev > > > -- > Best regards, Alexander Kanevskiy. > > > > --------------------------------------------------------------------- > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki Business Identity Code: > 0357606 - 4 Domiciled in Helsinki > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
