Right, Thanks. I have found the root cause. It is related with flag of x.
From: Manuel Bachmann [mailto:[email protected]]
Sent: Tuesday, September 2, 2014 5:11 PM
To: Wang, Quanxian
Cc: Ylinen, Mikko; [email protected]
Subject: Re: Any reason to add X11 flag in current wayland repo?
Quanxian,
Just rebuilt the package, seems to work fine.
I see that you were using a custom build.conf file ("-D
/home/qxwang/gbs/3.0-ivi/build_ivi_wayland.conf")
My understanding is that your config file enables the "%with x" flag (hence why
it is looking for "x11", "xext"...), but obviously the wayland repo which you
are building against doesn't provide any of these packages. It wasn't a problem
when the flag was missing - but you might have run into similar problems when
building other packages.
I have 2 suggestions :
- edit your "build_ivi_wayland.conf", so it defines "%with x" to 0, and "%with
wayland" to 1 ;
- use the "build.conf" file provided by the wayland repo itself
(http://download.tizen.org/snapshots/tizen/ivi/latest/repos/atom/packages/repodata/8c262bdf6b0207657429addd83717bd99a8a25b978d4a3810abe8fe89a41a25a-build.conf.gz
). gbs should already be using it now, as you deleted the "-D" option.
2014-09-02 8:37 GMT+02:00 Wang, Quanxian
<[email protected]<mailto:[email protected]>>:
From: Ylinen, Mikko
[mailto:[email protected]<mailto:[email protected]>]
Sent: Tuesday, September 2, 2014 2:04 PM
To: Wang, Quanxian
Cc: Manuel Bachmann; [email protected]<mailto:[email protected]>
Subject: Re: Any reason to add X11 flag in current wayland repo?
On Tue, Sep 2, 2014 at 4:55 AM, Wang, Quanxian
<[email protected]<mailto:[email protected]>> wrote:
Thanks Manuel Bachmann
Something like
What's the gbs command and repository you're using?
[Wang, Quanxian] This is my configuration file.
url = http://download.tizen.org/snapshots/tizen/ivi/latest/
gbs -c /home/qxwang/gbs/3.0-ivi/gbs.conf build --include-all -A i586 -B
/home/qxwang/GBS-ROOT/3.0-ivi/ -D
/home/qxwang/gbs/3.0-ivi/build_ivi_wayland.conf
I have deleted –D option, seems it works. The cause maybe my build.conf file. I
will check what the difference is with latest update.
-- Mikko
“
info: Generating patches from git
(upstream/10.1.3.<http://10.1.3.>.b66e90fb46c0d9415a68831d8e3db27a3546e1f1)
info: Generating diff file HEAD..b66e90fb46c0d9415a68831d8e3db27a3546e1f1
info: Didn't find any old 'Patch' tags, adding new patches after the last
'Source' tag.
info: Didn't find any old '%patch' macros, adding new patches after the last
'%setup' macro
fatal: Path 'MesaLib-10.1.3.tar.bz2.delta' does not exist in
'refs/heads/pristine-tar'
pristine-tar: git show refs/heads/pristine-tar:MesaLib-10.1.3.tar.bz2.delta
failed
error: Couldn't checkout "MesaLib-10.1.3.tar.bz2": /usr/bin/pristine-tar
returned 128
info: MesaLib-10.1.3.tar.bz2 does not exist, creating from 'upstream/10.1.3'
info: package files have been exported to:
/home/qxwang/GBS-ROOT/3.0-ivi/local/sources/current/mesa-10.1.3-0
info: retrieving repo metadata...
info: parsing package data...
info: building repo metadata ...
info: package dependency resolving ...
error: *** Error Summary ***
=== the following packages failed to build due to missing build dependencies
(1) ===
mesa:
nothing provides pkgconfig(x11)
nothing provides pkgconfig(x11-xcb)
nothing provides pkgconfig(xext)
nothing provides pkgconfig(xdamage)
nothing provides pkgconfig(xfixes)
nothing provides pkgconfig(dri2proto)
nothing provides pkgconfig(glproto)
nothing provides pkgconfig(xcb-dri2)
nothing provides pkgconfig(xcb-glx)
error: <gbs>rpmbuild fails
“
Regards
Quanxian Wang
From: Manuel Bachmann
[mailto:[email protected]<mailto:[email protected]>]
Sent: Monday, September 1, 2014 5:54 PM
To: Wang, Quanxian
Cc: [email protected]<mailto:[email protected]>
Subject: Re: Any reason to add X11 flag in current wayland repo?
HI Quanxian,
Thanks for asking. We need this flag because we integrate the X11 packages with
the Common profile, as described here :
https://lists.tizen.org/pipermail/dev/2014-July/003512.html
Normally, this flag will only be used on the x11 images, and most notably build
"libGL" which is needed to build xorg-server along with its latest extensions.
The pure wayland image should not be impacted AFAIK (and will not have libGL).
Could you describe the problem you encounter when building with GBS ? Any error
message ?
Regards,
2014-09-01 10:50 GMT+02:00 Wang, Quanxian
<[email protected]<mailto:[email protected]>>:
Hi, Manuel Bachmann
I could not build weston with latest mesa update. I found you add X11 flag in
mesa project.
commit 2ac8db2d91e54b3ac3bcb6f1d4d9f2a781fb2cff
Author: Manuel Bachmann
<[email protected]<mailto:[email protected]>>
Date: Sat Jul 5 09:35:02 2014 +0200
packaging: Re-enable X11 compiling
Change-Id: I202b022ed7fd37857d8e546d6ab50d439716f10b
Signed-off-by: Manuel Bachmann
<[email protected]<mailto:[email protected]>>
Signed-off-by: Jos<C3><A9> Bollo
[email protected]<mailto:[email protected]>
X11 flag has been deleted before to disable the dependency on X. I am not sure
why you add this flag? Only for GL support?
With patch, it will affect more packages which use egl when building.
Without your commit in my local machine, weston could be built out successfully
for wayland.
By the way, anyone comes across the same issue when you build the package which
uses egl? I am afraid maybe I miss something.
Regards
Thanks
Quanxian Wang
--
Regards,
Manuel BACHMANN
Tizen Project
VANNES-FR
_______________________________________________
IVI mailing list
[email protected]<mailto:[email protected]>
https://lists.tizen.org/listinfo/ivi
--
Regards,
Manuel BACHMANN
Tizen Project
VANNES-FR
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
