Here is the catch. Evas and Elementary git repositores are ok. The problem is from GBS repository server. Server has an old evas package. So the version evas from git and evas package from repository are different :( Evas package should be updated based on evas git.
Maybe I should ask SOMEONE(I don't know whom to ask) to update the evas package. But you can still build elementary by: 1. Build evas first 1.A Clone framework/uifw/evas 1.B $ git checkout tizen_2.0 1.C $ gbs build -A armv7l 2. Build elementary now 2.A $ cd elementary 2.B $ git checkout tizen_2.0 2.C $ gbs build -A armv7l Now elementary depends on locally built evas. You can use gbs local repository feature with -R. Please find more GBS documents from: https://source.tizen.org/documentation/gbs-build Thanks. Daniel Juyung Seo (SeoZ) On Thu, Mar 28, 2013 at 10:27 PM, Daniel Juyung Seo <seojuyu...@gmail.com> wrote: > Well I found out why. > > You are using master branch. Tizen 2.0 uses tizen_2.0 branch. So the > edje library and elementary library versions do not match. > So when you clone git from any tizen repositories, you should move to > tizen_2.0 branch by using: > $ git checkout tizen_2.0. > Tizen 2.0 alpha used master branch but it looks like the policy was > changed since Tizen 2.0. > > BUT here is another issue. > elementary tizen_2.0 branch has a build issue. I guess Evas library is > older than elementary :( > Someone pushed wrong version of EFL to tizen 2.0. > I will fix this soon. > > Thanks. > > Daniel Juyung Seo (SeoZ) > > > On Thu, Mar 28, 2013 at 7:31 PM, Carsten Haitzler <ti...@rasterman.com> wrote: >> On Tue, 19 Mar 2013 18:11:00 +0900 Jeong-Joon Yoo <jeongjoon....@gmail.com> >> said: >> >> if i am not mistaken the parser is complaining about these line of text: >> >> rel2.offset: 2 2; >> image { >> normal: "bt_sm_shine.png"; >> border: 6 6 6 0; >> } >> >> specifically the line with "normal"... can you check that this is the same >> for >> you? it was not long ago that i ran an obs build (well osc local build here) >> of >> elementary and it worked just fine. i am wondering what specifically about >> your >> setup causes this? in fact the parse stack is WRONG. it should be >> collections.group.parts.part.description.image.normal >> not >> collections.group.parts.part.description.image.image >> >> how is it replacing the last stack item with "image" instead of "normal" >> that's there in the src? i have never seen it just magically do this. the >> code >> to do that parsing is many years old and it's been put through a lot of >> testing across a wide range of os's and architectures, so chances are of the >> core parsing stack building/parsing having since a simple issue is very low, >> but something weird is happening to input that is not normal maybe? a locale >> thing? i don't think this should cause an issue here. >> >> i'm running a build .. but it'll take a while... (maybe another 30-40mins). >> >>> Hi tizen developers, >>> >>> When I build tizen with this command, >>> >>> elementary$ gbs build -A armv71 --include-all >>> >>> it returns some error messages after one hour build progress. >>> >>> < part of error >>> message>----------------------------------------------------------------- >>> >>> [ 1562s] [Eina] could not get cpu affinity: Function not implemented >>> [ 1562s] qemu: Unsupported syscall: 242 >>> [ 1562s] [Eina] could not get cpu affinity: Function not implemented >>> [ 1562s] qemu: Unsupported syscall: 242 >>> [ 1562s] [Eina] could not get cpu affinity: Function not implemented >>> [ 1562s] qemu: Unsupported syscall: 242 >>> [ 1562s] [Eina] could not get cpu affinity: Function not implemented >>> [ 1562s] qemu: Unsupported syscall: 242 >>> [ 1562s] [Eina] could not get cpu affinity: Function not implemented >>> [ 1563s] edje_cc: Error. ../../data/themes/widgets/gengrid.edc:1171 >>> got 1 arguments, but expected at least 2 >>> [ 1563s] edje_cc: Error. PARSE STACK: >>> [ 1563s] collections.group.parts.part.description.image.image >>> [ 1563s] edje_cc: Error. PARAMS: >>> [ 1563s] edje_cc: Error. bt_sm_shine.png >>> [ 1563s] make[3]: *** [default.edj] Error 255 >>> [ 1563s] make[3]: Leaving directory >>> `/home/abuild/rpmbuild/BUILD/elementary-1.0.0+svn.70492slp2 >>> +build25/data/themes' [ 1563s] make[2]: *** [all-recursive] Error 1 >>> [ 1563s] make[2]: Leaving directory >>> `/home/abuild/rpmbuild/BUILD/elementary-1.0.0+svn.70492slp2+build25/data' >>> [ 1563s] make[1]: *** [all-recursive] Error 1 >>> [ 1563s] make[1]: Leaving directory >>> `/home/abuild/rpmbuild/BUILD/elementary-1.0.0+svn.70492slp2+build25' >>> [ 1563s] make: *** [all] Error 2 >>> [ 1563s] error: Bad exit status from /var/tmp/rpm-tmp.jI8Q4U (%build) >>> [ 1563s] >>> [ 1563s] >>> [ 1563s] RPM build errors: >>> [ 1563s] Bad exit status from /var/tmp/rpm-tmp.jI8Q4U (%build) >>> warning: build failed, Leaving the logs in >>> /home/a1jjyoo/work/tizen/local/repos/tizen2.0/armv7l/logs/fail/elementary-1.0.0 >>> +svn.70492slp2+build25-1/log error: *** Error Summary *** >>> === the following packages failed to build due to rpmbuild issue === >>> elementary-tizen2.0-armv7l: >>> /home/a1jjyoo/work/tizen/local/repos/tizen2.0/armv7l/logs/fail/elementary-1.0.0 >>> +svn.70492slp2+build25-1/log >>> >>> error: <gbs>rpmbuild fails >>> >>> <end of the error >>> message>----------------------------------------------------------------- >>> >>> >>> Any helpful comment to solve this situation will be appreciated >>> >>> - jy >>> _______________________________________________ >>> General mailing list >>> General@lists.tizen.org >>> https://lists.tizen.org/listinfo/general >>> >> >> >> -- >> Carsten Haitzler (The Rasterman) <ti...@rasterman.com> >> _______________________________________________ >> General mailing list >> General@lists.tizen.org >> https://lists.tizen.org/listinfo/general _______________________________________________ General mailing list General@lists.tizen.org https://lists.tizen.org/listinfo/general
