Hi Tracy,

First off, thank you for your response!  I'm glad you're looking at the
mailing list. It is most appreciated.

I'm trying to build the latest 3.0 milestone. I just went ahead and put all
of this in my .gbs.conf intending eventually to use a "-P option" to select
between various profiles.


But just in case this was somehow causing the issue, I just now went ahead
and went back, removed all of GBS_ROOT, moved .gbs.root to a backup,
created a gbs.tizen-3.0.conf
in which I put a vanilla Tizen 3.0 profile
https://wiki.tizen.org/wiki/IVI/GBS_configuration_files_Tizen_IVI
By which I mean this:

[general]
profile = profile.tizen_3.0_m2_jul
editor = vim

[obs.tizen]
url = https://api.tizen.org
#user =
#passwdx =

[repo.tizen-3.0-dev]
url = 
http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages

[repo.tizen-3.0-m2-jul]
url = 
http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/repos/ivi/ia32/packages/

[profile.tizen_3.0_dev]
obs = obs.tizen
repos = repo.tizen-3.0-dev

[profile.tizen_3.0_m2_jul]
obs = obs.tizen
repos = repo.tizen-3.0-m2-jul

The same problem happened.  This is the tail of the output I got:

warning: build failed, Leaving the logs in
/home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.tizen.volume-0.2.4-1/log
info: updating local repo
error: *** Error Summary ***
=== the following packages failed to build due to missing build
dependencies (1) ===
wrt-setting:
  nothing provides pkgconfig(ace)
  nothing provides pkgconfig(ace-dao-rw)

=== the following packages failed to build due to rpmbuild issue (2) ===
org.tizen.app-selector-tizen_3.0_m2_jul-i586:
/home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.tizen.app-selector-0.1.0-76/log
org.tizen.volume-tizen_3.0_m2_jul-i586:
/home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.tizen.volume-0.2.4-1/log


Please understand that I know NOTHING about how Tizen IVI is supposed to be
organized. I'm just hooking up to the repositories in the way the
documentation say that they should. Is there something I'm missing?

Steve Maurer



On 19 August 2013 14:11, Graydon, Tracy <[email protected]> wrote:

> Hi Steven,
>
> Which branch of apps/core/preloaded/volume-app are you trying to build?
> The version number in the output is 0.2.4, which suggests you may be trying
> to build the master branch, which would be for Tizen 1.0, against the Tizen
> 3.0 repos. The Tizen 3.0 version of org.tizen.volume is 0.2.8. Hence my
> question.
>
> If you are trying to build for Tizen 3.0, you'll likely want to use the
> "tizen" branch instead of master.
>
> In general, for non-vertical-specific projects, branches map to versions
> as follows:
>
> master ---> Tizen 1.0
> 1.0_post --> Tizen 2.0Alpha
> 2.0  ---> Tizen 2.0
> tizen_2.1 ---> Tizen 2.1
> tizen_2.2 --> Tizen 2.2
> tizen --> Tizen 3.0
>
> For IVI-specific projects, under profile/ivi in Gerrit, branching is as
> follows:
>
> 1.0 ---> Tizen 1.0
> 2.0alpha --> Tizen 2.0alpha
> 2.0 --> Tizen 2.0
> 2.0alpha-wayland --> Wayland-related 2.0alpha IVI packages.
> tizen --> Tizen 3.0
>
> Note that IVI does not use master branch at all. In fact, no verticals in
> Tizen should have a master branch, since that is strictly mapped to the 1.0
> release line, which is frozen. Anything that came along after Tizen 1.0
> should not have a master branch. So, in theory, you won't find a master
> branch on Tizen Mobile projects either. Occasionally we find a stray where
> a master branch got created accidentally. Unless you are actually working
> with 1.o source, you may safely view master branches as poisonous and avoid
> them entirely. ;)
>
> Let us know if that doesn't help resolve the issue.
>
> Tracy
>
>
> From: <Maurer>, Steven <[email protected]<mailto:
> [email protected]>>
> Date: Monday, August 19, 2013 1:01 PM
> To: "[email protected]<mailto:[email protected]>" <[email protected]
> <mailto:[email protected]>>
> Subject: Another tizen build failure on the most recent release - nothing
> provides pkgconfig/mm-sound
>
> These seem to come up regularly on the mailing list, and I'm sure there is
> something dumb that I'm going here, but I can't figure out exactly what.
>
> Running in Ubuntu:  gbs build -A i586
>
> ..gbs seems to build most everything, except it runs into this:
>
> ...(deleted for brevity)
> [   14s] + cmake -DCMAKE_INSTALL_PREFIX=/opt/apps/org.tizen.volume
> [   14s] -- The C compiler identification is GNU 4.7.2
> [   14s] -- Check for working C compiler: /usr/bin/cc
> [   14s] -- Check for working C compiler: /usr/bin/cc -- works
> [   14s] -- Detecting C compiler ABI info
> [   14s] -- Detecting C compiler ABI info - done
> [   14s] Build type: Release
> [   14s] -- Found PkgConfig: /usr/bin/pkg-config (found version "0.28")
> [   14s] -- checking for modules
> 'appcore-efl;ecore-input;ecore-x;ecore;evas;edje;mm-sound;vconf;utilX;syspopup;bundle;svi;glib-2.0;ui-gadget-1'
> [   14s] --   package 'mm-sound' not found
> [   14s] CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:279
> (message):
> [   14s]   A required package was not found
> [   14s] Call Stack (most recent call first):
> [   14s]   /usr/share/cmake/Modules/FindPkgConfig.cmake:333
> (_pkg_check_modules_internal)
> [   14s]   CMakeLists.txt:32 (pkg_check_modules)
> [   14s]
> [   14s]
> [   14s] PO: /home/abuild/rpmbuild/BUILD/org.tizen.volume-0.2.4/po/ar.po
> [   14s] PO: /home/abuild/rpmbuild/BUILD/org.tizen.volume-0.2.4/po/bg.po
> ....(deleted for brevity)
> [   14s] -- Configuring incomplete, errors occurred!
> [   14s] error: Bad exit status from /var/tmp/rpm-tmp.UKGW85 (%build)
> [   14s]
> [   14s]
> [   14s] RPM build errors:
> [   14s]     Bad exit status from /var/tmp/rpm-tmp.UKGW85 (%build)
> warning: build failed, Leaving the logs in
> /home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.tizen.volume-0.2.4-1/log
> error: *** Error Summary ***
> === the following packages failed to build due to missing build
> dependencies (1) ===
> wrt-setting:
>   nothing provides pkgconfig(ace)
>   nothing provides pkgconfig(ace-dao-rw)
>
> === the following packages failed to build due to rpmbuild issue (2) ===
> org.tizen.app-selector-tizen_3.0_m2_jul-i586:
> /home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.tizen.app-selector-0.1.0-76/log
> org.tizen.volume-tizen_3.0_m2_jul-i586:
> /home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.tizen.volume-0.2.4-1/log
> error: <gbs>rpmbuild fails
>
>
> Here is my .gbs.conf, though I don't think it's that:
>
>
> [general]
> tmpdir = /var/tmp
> profile = profile.tizen_3.0_m2_jul
> editor = vim
> buildroot = ~/GBS-ROOT/
> packaging_branch = master
> upstream_branch = upstream
> upstream_tag = upstream/${upstreamversion}
> packaging_dir = packaging
> work_dir = .
> buildconf = ${work_dir}/tizen-conf/build.conf
>
> [profile.tizen]
> obs = obs.tizen
> repos = repo.tizen-3.0-m2-jul
>
> [obs.tizen]
> url = https://api.tizen.org
> user = smaurer
> passwdx = [...deleted...]]
>
> [repo.tizen-3.0-dev]
> url =
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages
>
> [repo.tizen-3.0-m2-jul]
> url =
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/repos/ivi/ia32/packages/
>
> [repo.tizen_latest]
> url = http://download.tizen.org/releases/trunk/daily/ivi/latest/
>
> [profile.tizen_3.0_dev]
> obs = obs.tizen
> repos = repo.tizen-3.0-dev
>
> [profile.tizen_3.0_m2_jul]
> obs = obs.tizen
> repos = repo.tizen-3.0-m2-jul
>
> -----
>
> I've also looked into comparing this package to others in the distro:
>
> % find . -name '*mm-sound*' -print
>
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/etc/smack/accesses.d/libmm-sound
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/installed-pkg/libmm-sound
>
> ./GBS-ROOT/local/cache/fcfcf90f21d1c113224d1a244d20708f/libmm-sound-0.7.2-1.4.i686.rpm
>
> ...a more normal package from the same line looks like this:
>
> % find . -name '*appcore-efl*' -print
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/usr/lib/libappcore-efl.so.1.1
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/usr/lib/libappcore-efl.so.1
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/usr/lib/libappcore-efl.so
>
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/usr/lib/pkgconfig/appcore-efl.pc
>
> ./GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/usr/include/appcore/appcore-efl.h
>
> You will notice the appcore-efl.pc file is present, while the mm-sound.pc
> file is missing.
>
> Does anyone have any ideas as to why mm-sound isn't working?
> Is there some funky way to create the appropriate pkg-config file for it?
> I'm really at a dead end.
>
> --
> Kind Regards
>
> Steven Maurer
> -------------------
> Infotainment Engineer
> MSX on behalf of Jaguar Land Rover
> One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland,
> Oregon, 97204
>
> Email: [email protected]<mailto:[email protected]>
>
>


-- 
Kind Regards

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

Email: [email protected]
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to