[Tizen General] Missing Dependencies in the Local Package Build of Tizen 2.2

Zhang, Qiang Z qiang.z.zhang at intel.com
Fri Sep 6 16:41:23 GMT 2013


Hi Martin,

It's not difficult issue, and very easy to resolve.

When you update .gbs.conf, the pre-built local repo, cloned by repo sync, has not been included in .gbs.conf, see full example of gbs in
https://source.tizen.org/documentation/reference/git-build-system/creating-tizen-platform-image-scratch


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

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

[repo.tizen2.2_x86]
url=${work_dir}/pre-built/toolchain-x86/
                                               g

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

[profile.tizen2.2]
repos=repo.tizen2.2_arm, repo.tizen2.2_x86, repo.tizen2.2
buildconf=${work_dir}/scm/meta/build-config/build.conf

So, what you need to do is add tizen 2.2 pre-built to you gbs.conf, pre-built repo contains the missing dependencies.

Thanks
Qiang




From: general-bounces at lists.tizen.org [mailto:general-bounces at lists.tizen.org] On Behalf Of Martin Hennelly
Sent: Tuesday, September 03, 2013 11:03 PM
To: Hanchett, Paul
Cc: general at lists.tizen.org; product-dev at lists.tizen.org
Subject: Re: [Tizen General] Missing Dependencies in the Local Package Build of Tizen 2.2

HI Paul,

I've cloned using $repo init -u ssh://<username>@review.tizen.org:29418/scm/manifest -b tizen_2.2, then $repo sync.

When I try to build at the top-level, I am using
$ accel_pkgs="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"
$ gbs build -A armv7l --threads=4 --clean-once --exclude=${accel_pkgs},filesystem,aul,libmm-sound,libtool -debug

I've tried various things today:
Modify .gbs.conf for local repo; chroot command to GBS command line; gbs - R for local repository;  clean up .gbs.conf to the minimum; try different architectures,....
Still I get the wrong path to depanneur.

Tomorrow I'll try and hack depanneur to a fixed path (although I don't know python) and see if at least the system level build would start

Regards - Martin

From: Hanchett, Paul [mailto:phanchet at jaguarlandrover.com]
Sent: 03 September 2013 02:07
To: Martin Hennelly
Cc: general at lists.tizen.org<mailto:general at lists.tizen.org>; product-dev at lists.tizen.org<mailto:product-dev at lists.tizen.org>
Subject: Re: [Tizen General] Missing Dependencies in the Local Package Build of Tizen 2.2

You're welcome for whatever help I may have provided!

We've been working to get a successful build of Tizen 3.0, and it's been quite a challenge!  We feel like we're slowly getting it figured out but until we actually succeed it's hard to say if we are actually making progress.  You know how it goes!  :-(

I'm puzzled by the path you highlighted, too.  What does your gbs command line look like? Did you use repo to get the project repository set?

(We *think*) We've had synchronization problems between the manifest and the actual repositories needed by the project (not sure how to say that better...). It's led to naming mismatches in the libraries. But I wouldn't expect to see that sort of issue on the 12.2 release.

Are you trying to do this on the released version of 2.2 or one of the snapshots?

Paul

Paul Hanchett
-------------------
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204

Email: phanchet at jaguarlandrover.com<mailto:phanchet at jaguarlandrover.com>
-------------------

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070

On Mon, Sep 2, 2013 at 7:50 AM, Martin Hennelly <Martin.Hennelly at nectech.co.uk<mailto:Martin.Hennelly at nectech.co.uk>> wrote:
Thanks for Paul for your advice.  I was now able to make a build of an individual module following the info in the link you sent - basically my .gbs.conf was not set to use the pre-built tools.  I adjusted my top-level and local .gbs.conf as shown below and I could build an individual module

I am using gbs version 18.  I was always able to build individual modules of the previous Tizen releases.  However a system build was not possible due to cyclic dependencies.

I am still not able to perform a system level build even following the info in the link you sent


The system level build still fails due to the incorrect path being passed to depanneur.

So when I try and build at the system level in the folder /home/nec/Tizen/Tizen2_2 I get the incorrect path passed to depanneur and not surprisingly no code can be found.:

depanneur --arch=armv7l --repository=/home/nec/Tizen/Tizen2_2/pre-built/toolchain-arm/ --repository=/home/nec/Tizen/Tizen2_2/pre-built/toolchain-x86/ --repository=http://download.tizen.org/releases/2.2/tizen-2.2/repos/tizen-base/armv7l/packages --repository=http://download.tizen.org/releases/2.2/tizen-2.2/repos/tizen-main/armv7l/packages --dist=tizen2.2 --configdir=/var/tmp/nec-gbs --path=/home/nec --exclude=bash --exclude=bzip2-libs --exclude=c-ares --exclude=cmake --exclude=coreutils --exclude=diffutils --exclude=eglibc --exclude=elfutils-libelf --exclude=elfutils-libs --exclude=elfutils --exclude=fdupes --exclude=file --exclude=findutils --exclude=gawk --exclude=gmp --exclude=gzip --exclude=libacl --exclude=libattr --exclude=libcap --exclude=libcurl --exclude=libfile --exclude=libgcc --exclude=liblua --exclude=libstdc++ --exclude=make --exclude=mpc --exclude=mpfr --exclude=ncurses-libs --exclude=nodejs --exclude=nspr --exclude=nss-softokn-freebl --exclude=nss --exclude=openssl --exclude=patch --exclude=popt --exclude=rpm-build --exclude=rpm-libs --exclude=rpm --exclude=sed --exclude=sqlite --exclude=tar --exclude=xz-libs --exclude=zlib --exclude=binutils --exclude=gcc --exclude=filesystem --exclude=aul --exclude=libmm-sound --exclude=libtool --clean-once --debug --threads=2 --packaging-dir=packaging --upstream-branch=upstream

Result in error:
error: No source package found at /home/nec


and when I build at the individual module level, the right path is selected from the directory in which I run the gbs command:

depanneur --arch=armv7l --repository=/home/nec/Tizen/Tizen2_2/pre-built/toolchain-arm/ --repository=/home/nec/Tizen/Tizen2_2/pre-built/toolchain-x86/ --repository=http://download.tizen.org/releases/2.2/tizen-2.2/repos/tizen-base/armv7l/packages --repository=http://download.tizen.org/releases/2.2/tizen-2.2/repos/tizen-main/armv7l/packages --dist=tizen2.2 --configdir=/var/tmp/nec-gbs --path=/home/nec/Tizen/Tizen2_2/framework/messaging/msg-service --exclude=bash --exclude=bzip2-libs --exclude=c-ares --exclude=cmake --exclude=coreutils --exclude=diffutils --exclude=eglibc --exclude=elfutils-libelf --exclude=elfutils-libs --exclude=elfutils --exclude=fdupes --exclude=file --exclude=findutils --exclude=gawk --exclude=gmp --exclude=gzip --exclude=libacl --exclude=libattr --exclude=libcap --exclude=libcurl --exclude=libfile --exclude=libgcc --exclude=liblua --exclude=libstdc++ --exclude=make --exclude=mpc --exclude=mpfr --exclude=ncurses-libs --exclude=nodejs --exclude=nspr --exclude=nss-softokn-freebl --exclude=nss --exclude=openssl --exclude=patch --exclude=popt --exclude=rpm-build --exclude=rpm-libs --exclude=rpm --exclude=sed --exclude=sqlite --exclude=tar --exclude=xz-libs --exclude=zlib --exclude=binutils --exclude=gcc --exclude=filesystem --exclude=aul --exclude=libmm-sound --exclude=libtool --clean-once --debug --threads=2 --packaging-dir=packaging --upstream-branch=upstream

results in build success.

Many thanks again Paul for your advice - I'll press on and have another look at the system level build

Regards - Martin


~/.gbs.conf

[general]

tmpdir = /var/tmp
editor =
packaging_branch = master
upstream_branch = upstream
upstream_tag = upstream/${upstreamversion}
packaging_dir = packaging
profile = profile.tizen2.2
buildroot = ~/GBS-ROOT/
user = [uname]
passwdx = [pword_hash]

~/Tizen/Tizen2_2/.gbs.conf

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

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

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

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

[profile.tizen2.2]
repos=repo.tizen2.2_arm, repo.tizen2.2_x86, repo.tizen2.2
buildconf=${work_dir}/scm/meta/build-config/build.conf



From: Hanchett, Paul [mailto:phanchet at jaguarlandrover.com<mailto:phanchet at jaguarlandrover.com>]
Sent: 30 August 2013 17:27
To: Martin Hennelly
Cc: general at lists.tizen.org<mailto:general at lists.tizen.org>; product-dev at lists.tizen.org<mailto:product-dev at lists.tizen.org>
Subject: Re: [Tizen General] Missing Dependencies in the Local Package Build of Tizen 2.2

Hey Martin--

In the spirit of one blind man helping another, have you followed the recent conversations about doing local tizen builds from scratch?  In particular look at the manifest switch (-m) in the example here<https://www.google.com/url?q=https%3A%2F%2Fsource.tizen.org%2Fdocumentation%2Fdeveloper-guide%2Fcreating-tizen-platform-image-scratch-through-local-build&sa=D&sntz=1&usg=AFrqEzczKXPylm0MqcYt3_h-tQpYkKr-Bw>.

As I look at the docs though, it doesn't look like they've used -m in the 2.2 repo example... And I've no idea of how to handle it if you already have your repository tree in place, sorry.

Did it build at some previous time?  :-)

Paul



Paul Hanchett
-------------------
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204

Email: phanchet at jaguarlandrover.com<mailto:phanchet at jaguarlandrover.com>
-------------------

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070

On Fri, Aug 30, 2013 at 6:51 AM, Martin Hennelly <Martin.Hennelly at nectech.co.uk<mailto:Martin.Hennelly at nectech.co.uk>> wrote:
HI All,
I am getting an error trying to build a local build of a single module of Tizen 2.2 on Ubuntu12.04 LTS.  This could be happening because Ubuntu 12.04 used up-versioned and renamed packages.  The build error I get is basically for missing dependencies.  I can't really work around this error as I do not control the manifest file and so cannot patch it.  Could Samsung please provide a workaround in the manifest?

The build error basically results in missing dependencies:
debug: expansion error
debug:   nothing provides libxml2-x86-arm needed by cmake-x86-arm
debug:   nothing provides libcurl-x86-arm needed by cmake-x86-arm
debug:   nothing provides expat-x86-arm needed by cmake-x86-arm
debug:   nothing provides c-ares-x86-arm needed by cmake-x86-arm
The full debug listing and .gbs.conf may be seen below.
My Linux Configuration is this:
$  cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.2 LTS"
NAME="Ubuntu"
VERSION="12.04.2 LTS, Precise Pangolin"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu precise (12.04.2 LTS)"
VERSION_ID="12.04"

$ uname -a
Linux DTizen 3.5.0-24-generic #37~precise1-Ubuntu SMP Thu Feb 7 22:09:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux


Regards - Martin
(there is nothing special about the module I try to build  - the same behaviour happens with all.  Likewise I have added various build extensions like -clean and -include-all and the result is the same)
[mymachine]:~/Tizen/Tizen2_2/framework/system/libslp-sensor$ gbs build -A armv7l --debug
gbp:debug: git rev-parse --is-bare-repository
gbp:debug: git rev-parse --git-dir
gbp:debug: git rev-parse --show-toplevel
gbs:info: generate repositories ...
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/repodata/repomd.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/repomd.xml
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/repodata/repomd.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/repomd.xml
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/builddata/build.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/build.xml
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/builddata/0fa267f9b5c2439349e22f9049e3f5b421e7d97bcc36f0a8254963f0fb5660f0-build.conf => /var/tmp/nec-gbs/gbscacheO9a9DQ/0fa267f9b5c2439349e22f9049e3f5b421e7d97bcc36f0a8254963f0fb5660f0-build.conf
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/repos/tizen-base/armv7l/packages/repodata/repomd.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/repomd.xml
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/repos/tizen-base/armv7l/packages/repodata/repomd.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/repomd.xml
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/repos/tizen-base/source/repodata/repomd.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/repomd.xml
gbs:debug: fetching http://download.tizen.org/releases/2.2/latest/repos/tizen-base/source/repodata/repomd.xml => /var/tmp/nec-gbs/gbscacheO9a9DQ/repomd.xml
gbs:debug: running command: depanneur --arch=armv7l --repository=http://[uname]:[pword]@download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/<http://download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/> --repository=http://martinh:Paragon29@download.tizen.org/releases/2.2/latest/repos/tizen-base/armv7l/packages/ --repository=http://[uname]:[pword]@download.tizen.org/releases/2.2/latest/repos/tizen-base/source/<http://download.tizen.org/releases/2.2/latest/repos/tizen-base/source/> --dist=tizen --configdir=/var/tmp/nec-gbs --path=/home/nec/Tizen/Tizen2_2/framework/system/libslp-sensor --debug --threads=1 --packaging-dir=packaging --upstream-branch=upstream
info: start building packages from: /home/nec/Tizen/Tizen2_2/framework/system/libslp-sensor (git)
debug: working on /home/nec/Tizen/Tizen2_2/framework/system/libslp-sensor
debug: my_system: cd /home/nec/Tizen/Tizen2_2/framework/system/libslp-sensor; git show HEAD:packaging >/tmp/WMgynSu0wV 2>/dev/null
info: prepare sources...
debug: my_system: cd /home/nec/Tizen/Tizen2_2/framework/system/libslp-sensor; git show HEAD:packaging/sensor.spec >/tmp/PMKy3imFrR/sensor.spec 2>/dev/null
info: retrieving repo metadata...
debug: my_system: > /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.local
debug: my_system: /usr/lib/build/createrpmdeps /home/nec/GBS-ROOT-profile.tizen/local/repos/tizen/armv7l/RPMS >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.local
debug: my_system: echo D: >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.local
debug: my_system: > /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: /usr/lib/build/createrepomddeps --cachedir=/home/nec/GBS-ROOT-profile.tizen/local/cache http://download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/ >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: /usr/lib/build/createrepomddeps --cachedir=/home/nec/GBS-ROOT-profile.tizen/local/cache http://download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/ >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: echo D: >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: /usr/lib/build/createrepomddeps --cachedir=/home/nec/GBS-ROOT-profile.tizen/local/cache http://download.tizen.org/releases/2.2/latest/repos/tizen-base/armv7l/packages/ >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: /usr/lib/build/createrepomddeps --cachedir=/home/nec/GBS-ROOT-profile.tizen/local/cache http://download.tizen.org/releases/2.2/latest/repos/tizen-base/armv7l/packages/ >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: echo D: >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: /usr/lib/build/createrepomddeps --cachedir=/home/nec/GBS-ROOT-profile.tizen/local/cache http://download.tizen.org/releases/2.2/latest/repos/tizen-base/source/ >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: /usr/lib/build/createrepomddeps --cachedir=/home/nec/GBS-ROOT-profile.tizen/local/cache http://download.tizen.org/releases/2.2/latest/repos/tizen-base/source/ >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: echo D: >> /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote
debug: my_system: cat /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.local /home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache.remote >/home/nec/GBS-ROOT-profile.tizen/local/order/.repo.cache
info: parsing package data...
info: building repo metadata ...
info: package dependency resolving ...
debug: Checking dependencies for sensor
debug: expansion error
debug:   nothing provides libxml2-x86-arm needed by cmake-x86-arm
debug:   nothing provides libcurl-x86-arm needed by cmake-x86-arm
debug:   nothing provides expat-x86-arm needed by cmake-x86-arm
debug:   nothing provides c-ares-x86-arm needed by cmake-x86-arm
debug: Checking dependencies for sensor
debug: expansion error
debug:   nothing provides libxml2-x86-arm needed by cmake-x86-arm
debug:   nothing provides libcurl-x86-arm needed by cmake-x86-arm
debug:   nothing provides expat-x86-arm needed by cmake-x86-arm
debug:   nothing provides c-ares-x86-arm needed by cmake-x86-arm
debug: my_system: sudo /bin/echo -n
info: package dependency:
sensor:
error: *** Error Summary ***
=== the following packages failed to build due to missing build dependencies (1) ===
sensor:
  nothing provides libxml2-x86-arm needed by cmake-x86-arm
  nothing provides libcurl-x86-arm needed by cmake-x86-arm
  nothing provides expat-x86-arm needed by cmake-x86-arm
  nothing provides c-ares-x86-arm needed by cmake-x86-arm


gbs:error: Traceback (most recent call last):
  File "/usr/bin/gbs", line 539, in <module>
    sys.exit(main(sys.argv))
  File "/usr/bin/gbs", line 533, in main
    return module.main(args)
  File "/usr/lib/pymodules/python2.7/gitbuildsys/cmd_build.py", line 323, in main
    raise GbsError('rpmbuild fails')
GbsError: <gbs>rpmbuild fails

My .gbs.conf file is this like:


[general]
#Current profile name which should match a profile section name
tmpdir = /var/tmp
editor =
packaging_branch = master
upstream_branch = upstream
upstream_tag = upstream/${upstreamversion}
packaging_dir = packaging
profile = profile.tizen
buildroot = ~/GBS-ROOT/
work_dir = ~/Tizen/Tizen2_2


[profile.tizen]
# If no buildroot for profile, the buildroot in general section will be used
buildroot = ~/GBS-ROOT-profile.tizen/
# Specify build conf for a specific profile by using shell-style variable references
buildconf = ${work_dir}/scm/meta/build-config/build.conf
#Common authentication info for whole profile
user = [uname]
#CAUTION: please use the key name "passwd" to reset plaintext password
passwdx = [hash_of_pword]
#Comma separated list of repositories
repos = repo.tizen_main, repo.tizen_base


[repo.tizen_base]
url = http://download.tizen.org/releases/2.2/latest/repos/tizen-base/armv7l/packages/

[repo.tizen_main]
url = http://download.tizen.org/releases/2.2/latest/repos/tizen-main/armv7l/packages/

________________________________

NEC Technologies (UK) Ltd.,
Company Registered Office: Imperium, Reading, Berkshire, RG2 0TD
Registered Number: 4072718
Attention:
The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies.

_______________________________________________
General mailing list
General at lists.tizen.org<mailto:General at lists.tizen.org>
https://lists.tizen.org/listinfo/general



Click here<https://www.mailcontrol.com/sr/iNYHj5VwI9PGX2PQPOmvUnFKm77zQC2tfeyFyM7uZce2fNJhy9j+Nwg8Qu!faxTN41CAOKbjhdD3Y22mGO5KhQ==> to report this email as spam.

________________________________

NEC Technologies (UK) Ltd.,
Company Registered Office: Imperium, Reading, Berkshire, RG2 0TD
Registered Number: 4072718
Attention:
The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies.


________________________________

NEC Technologies (UK) Ltd.,
Company Registered Office: Imperium, Reading, Berkshire, RG2 0TD
Registered Number: 4072718
Attention:
The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/general/attachments/20130906/82e17bb5/attachment-0001.html>


More information about the General mailing list