Hi Ilya,

Thanks for your mail, please see my comments below.


Regards,
Jing Yang
At 2015-05-05 18:51:40, "Ilya Palachev" <[email protected]> wrote:
>Hi Jing Yang.
>
>Can you say how  to reproduce your error?

>
I synced the Tizen common source with manifest 
tizen-3.0.2015.Q1-common_20150331.1_arm-wayland.xml, below are the steps:


$ repo init -u ssh://[email protected]:29418/scm/manifest -b tizen -m 
common.xml
$ wget 
http://download.tizen.org/releases/milestone/tizen/common-3.0.2015.Q1/tizen-3.0.2015.Q1-common_20150331.1/builddata/manifest/tizen-3.0.2015.Q1-common_20150331.1_arm-wayland.xml
 -O .repo/manifests/common/projects.xml
$ repo sync -j32


>Can you please attach:

>  - your build command (osc or gbs)
1. Before building, update build.conf first
$ curl 
http://download.tizen.org/releases/milestone/tizen/common-3.0.2015.Q1/tizen-3.0.2015.Q1-common_20150331.1/repos/arm-wayland/packages/repodata/282308b3a5ce86ececb9600eb7981c5866608b71b71f147903e4751f49f59e14-build.conf.gz
 | gunzip > scm/meta/build-config/build.conf
2. Build command
$  gbs build -A armv7l --baselibs --threads=8


>  - your GBS config
I don't do any modification in .gbs.conf.


>  - your build config
Only download the build.conf from tizen website and replace the corresponding 
file in scm/meta/build-config/build.conf.
$ curl 
http://download.tizen.org/releases/milestone/tizen/common-3.0.2015.Q1/tizen-3.0.2015.Q1-common_20150331.1/repos/arm-wayland/packages/repodata/282308b3a5ce86ececb9600eb7981c5866608b71b71f147903e4751f49f59e14-build.conf.gz
 | gunzip > scm/meta/build-config/build.conf


>  - your changes to spec-file, build scripts etc (if any).
I don't do any modification in spec-file.


>
>AFAIK all my changes related with XWALK-3033 have already been accepted 
>to Tizen:{Common,Mobile,TV,Wearable} projects.
>The last profile that did not accepted it was IVI. That's why the bug is 
>still in "unresolvable" state and we are waiting for IVI RE response for 

>that.
Thanks for your information.


>
>You have mentioned the request 32619 but it seems to me that it does not 
>deal with this problem. Maybe you pasted the link with typo?

>The request has been accepted.
From the operation history in https://review.tizen.org/gerrit/#/c/32370, the 
last one is:
Robot Tizen
Feb 3 8:05 PM
↩

Patch Set 2:

The SR (Submit Request) has been *rejected* to OBS Tizen:Mobile project.

Reviewer: alone
Comments: SR 32619 is set to declined
Git project: platform/framework/web/crosswalk
Tag:submit/tizen_mobile/20150129.000000
Request URL:https://build.tizen.org/request/show/32619
From the link above, it shows the state for the request is revoked.
I checked the source in crosswalk.spec, it does have the changes you made in 
the JIRA...very strange.


>
>--
>Best regards,
>Ilya Palachev
>
>On 05.05.2015 05:34, Jing Yang wrote:
>> Hi All,
>>
>> I try to build tizen common source on ARM with 
>> milestone: tizen-3.0.2015.Q1-common_20150331.1.
>> Manifest:http://download.tizen.org/releases/milestone/tizen/common-3.0.2015.Q1/tizen-3.0.2015.Q1-common_20150331.1/builddata/manifest/tizen-3.0.2015.Q1-common_20150331.1_arm-wayland.xml
>> But meet building error like following:
>>
>> ...
>> [  525s] [317/6022] CXX 
>> obj/third_party/protobuf/src/google/protobuf/protobuf_full_do_not_use.text_format.o
>> [  527s] [318/6022] CXX 
>> obj/third_party/protobuf/src/google/protobuf/io/protobuf_full_do_not_use.printer.o
>> [  527s] FAILED: if [ ! -e libffmpegsumo.so -o ! -e 
>> libffmpegsumo.so.TOC ]; then cc -shared -Wl,--no-keep-memory 
>> -Wl,-z,now -Wl,-z,relro -pthread -Wl,-z,noexecstack -fPIC 
>> -fuse-ld=gold -Wl,--disable-new-dtags -Wl,-Bsymbolic 
>> -Lgen/third_party/ffmpeg -Wl,--icf=safe -Wl,-O1 -Wl,--as-needed 
>> -Wl,--gc-sections -o libffmpegsumo.so -Wl,-soname=libffmpegsumo.so 
>> @libffmpegsumo.so.rsp && { readelf -d libffmpegsumo.so | grep SONAME ; 
>> nm -gD -f p libffmpegsumo.so | cut -f1-2 -d' '; } > 
>> libffmpegsumo.so.TOC; else cc -shared -Wl,--no-keep-memory -Wl,-z,now 
>> -Wl,-z,relro -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold 
>> -Wl,--disable-new-dtags -Wl,-Bsymbolic -Lgen/third_party/ffmpeg 
>> -Wl,--icf=safe -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -o 
>> libffmpegsumo.so -Wl,-soname=libffmpegsumo.so @libffmpegsumo.so.rsp && 
>> { readelf -d libffmpegsumo.so | grep SONAME ; nm -gD -f p 
>> libffmpegsumo.so | cut -f1-2 -d' '; } > libffmpegsumo.so.tmp && if ! 
>> cmp -s libffmpegsumo.so.tmp libffmpegsumo.so.TOC; then mv 
>> libffmpegsumo.so.tmp libffmpegsumo.so.TOC ; fi; fi
>> [  527s] /usr/bin/ld.gold: error: 
>> /emul/i586-for-arm//usr/lib/gcc/armv7l-tizen-linux-gnueabi/4.9/liblto_plugin.so:
>>  
>> could not load plugin library: 
>> /emul/i586-for-arm//usr/lib/gcc/armv7l-tizen-linux-gnueabi/4.9/liblto_plugin.so:
>>  
>> cannot open shared object file: No such file or directory
>> [  527s] collect2: error: ld returned 1 exit status
>> [  554s] ninja: build stopped: subcommand failed.
>> [  554s] error: Bad exit status from /var/tmp/rpm-tmp.JZ5biE (%build)
>>
>> I see this issue has been resolved before in Feb 2015:
>> https://crosswalk-project.org/jira/browse/XWALK-3033
>> https://bugs.tizen.org/jira/browse/TC-2397
>>
>> Finally, I find the modification was rejected and revoked, see: 
>> https://build.tizen.org/request/show/32619
>> I'm curious about how the server could pass building without any 
>> error? Is there any plan for fixing it?
>>
>> Thanks
>>
>> Jing Yang
>>
>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to