[Dev] Tizen 2.2 armv7l local build error

N S S R Murthy nssr.murthy at inedasystems.com
Fri Oct 10 07:39:31 GMT 2014

Thank you Rui for giving some valuable suggestions on build. 
As suggested in https://lists.tizen.org/pipermail/dev/2014-October/004401.html, we have moved to Tizen 3.0 common. 
So far local builds are going fine. 

But our goal is to port Tizen on MIPS, for which we need pre-built/toolchain-mips and RPMS in that. 
Another thread active on this is: https://lists.tizen.org/pipermail/dev/2014-October/004496.html 

Andriy says it takes few weeks for them to write up the wiki and share the helper scripts to build toolchain rpms. 
We are in a kind of hurry and looking to progress on this. Can you suggest something? 

Murthy NSSR. 

----- Original Message -----

From: "RuiX Lv" <ruix.lv at intel.com> 
To: "N S S R Murthy" <nssr.murthy at inedasystems.com>, dev at lists.tizen.org 
Sent: Friday, October 10, 2014 11:58:30 AM 
Subject: RE: Tizen 2.2 armv7l local build error 

Hi Murthy, 

I’ve reproduced the error and have retriggered full build after excluding system-server. 
Will update you on the build result once local full build finishes on my side. 

The trick is, when encountering circle during local full build, 
we can break the circle by excluding one of the packages in the circle chain. 

The question followed is: which one is the perfect candidate? 
The general rule is as follows: 
· Do NOT exclude packages that have local changes. 
Developers make change to certain package for a reason. 
So excluding this kind of packages is NOT a wise choice. 
· Priority should be given to those already included in pre-built binaries. 
Since pre-built binaries can provide this kind of packages, 
excluding them has no impact on local full build, so feel free to exclude them. 
· Excluding any package (not that special, of course) in the circle can break the build circle and make the local full build go back to normal track. 


From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of N S S R Murthy 
Sent: Wednesday, October 01, 2014 6:01 PM 
To: dev at lists.tizen.org 
Subject: [Dev] Tizen 2.2 armv7l local build error 


I am trying to build Tizen 2.2 snapshot locally for armv7l. 
I have followed the steps to the word from : https://source.tizen.org/documentation/developer-guide/getting-started-guide/building-packages-locally-gbs#build-concepts 

The build went fine for sometime and failed with this error; please suggest. 

warning: mmfw-sysconf-simulator: build arch not compatible: i386 i486 i586 i686 athlon 
info: building repo metadata ... 
info: resolving skipped packages ... 
info: package dependency resolving ... 
warning: circle found: app-svc->pkgmgr-info->system-server->notification->app-svc 
info: circle found, exit... 
error: Traceback (most recent call last): 
File "/usr/bin/gbs", line 602, in <module> 
File "/usr/bin/gbs", line 596, in main 
return module.main(args) 
File "/usr/lib/pymodules/python2.7/gitbuildsys/cmd_build.py", line 376, in main 
raise GbsError('some packages failed to be built') 
GbsError: <gbs>some packages failed to be built 

build command used: gbs -v build -A armv7l --threads=6 --clean-once 
my .gbs.conf file is: 

profile = profile.tizen2.2 



exclude_packages=bash,bzip2-libs,c-ares,cmake,coreutils,diffutils,eglibc,elfutils-libelf,elfutils-libs,elfutils,fdupes,file,findutils,gawk,gmp,gzip,libacl,libattr,libcap,libcurl,libfile,libgcc,liblua,libstdc++,make,mpc,mpfr,ncurses-libs,nodejs,nspr,nss- softokn-freebl,nss,openssl,patch,popt,rpm-build,rpm-libs,rpm,sed,sqlite,tar,xz-libs,zlib,binutils,gcc,filesystem,aul,libmm-sound,libtool,syspopup 

The "syspopup" is added to excludes by looking at " https://developer.tizen.org/forums/general-support/warning-circle-found-syspopup " in which similar problem is reported. 
But my build problem persisted even after adding syspopup to excludes. Your helps is much appreciated. 

Murthy NSSR, 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20141010/4a35b8f1/attachment.html>

More information about the Dev mailing list