[Dev] Tizen 2.2 armv7l local build error

Lv, RuiX ruix.lv at intel.com
Fri Oct 10 06:28:30 GMT 2014


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.

Rui

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

Hi,

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>
    sys.exit(main(sys.argv))
  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:

[general]
tmpdir=/var/tmp/
profile = profile.tizen2.2
work_dir=.

[repo.tizen2.2_arm]
url=${work_dir}/pre-built/toolchain-arm/

[repo.tizen2.2]
url=http://download.tizen.org/snapshots/2.2/common/tizen-2.2_20140122.2/

[profile.tizen2.2]
repos=repo.tizen2.2_arm,repo.tizen2.2
buildconf=${work_dir}/scm/meta/build-config/build.conf
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.
Regards,
Murthy NSSR,

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


More information about the Dev mailing list