Hi JF Ding,

Thanks for your reply.
It shouldn't be related with network connections. I should give error 
information in the previous mail.
Following are more details:
1. sync code with arm based manifest tizen-3.0.m14.3-ivi_20141028.3_arm.xml;
2. prepare pre-built binaries with command:
$ cd ~/tizen_ivi_src/pre-built/toolchain-arm
$ ./tools/update_prebuilt.py -L .-R 
http://download.tizen.org/snapshots/tizen/ivi-3.0.m14.3/tizen-3.0.m14.3-ivi_20141028.3/repos/arm/packages/


When running update_prebuilt.py, it will generate error like:
...
downloading python-rpm
Traceback (most recent call last):
  File "./tools/update_prebuilt.py", line 90, in <module>
    pkgurl = args.remote_repo + '/' + remote_packages[pkgname].location
KeyError: 'cpp49'


After studying update_prebuilt.py, I find it will download primary.xml.gz from 
remote to local and parse it to create download package dict remote_packages, 
but parse another local file repodata/*.primary.xml.gz to get the file package 
location for downloading. At this time, these two primary.xml.gz files are 
different, for example, there's "python-rpm" from the download primary.xml.gz 
file, but can't find corresponding files from repodata/*.primary.xml.gz. Then 
python "KeyError: 'cpp49'" happens.


I replaced local file repodata/*.primary.xml.gz with the remote file, then it 
could download all pre-built binaries sucessfully.


But during building, it fails to build c-ares-1.7.5-1, the error message for 
c-ares-1.7.5-1 is:
... 
[   84s] Use of uninitialized value $item in exists at 
/usr/share/automake-1.14/Automake/General.pm line 60, <GEN55> line 613.
[   84s] Use of uninitialized value $item in hash element at 
/usr/share/automake-1.14/Automake/General.pm line 62, <GEN55> line 613.
[   84s] Use of uninitialized value $item in exists at 
/usr/share/automake-1.14/Automake/General.pm line 60.
[   84s] Use of uninitialized value $item in hash element at 
/usr/share/automake-1.14/Automake/General.pm line 62.
[   87s] Use of uninitialized value $m4dir in opendir at /bin/aclocal line 378.
[   87s] Use of uninitialized value $m4dir in concatenation (.) or string at 
/bin/aclocal line 381.
[   87s] aclocal: error: couldn't open directory '': No such file or directory
[   88s] autoreconf: aclocal failed with exit status: 1
[   88s] error: Bad exit status from /var/tmp/rpm-tmp.FlvzfM (%build)


So I want to know does anyone could pass building step by step without any 
errors according to the ivi snapshot building guide.


Thanks


Regards,
Jing Yang



At 2015-03-09 15:18:16, "JF Ding" <[email protected]> wrote:

According your message, it should be a simple network downloading issue. Please 
try the readonly cgit mirror for the big git trees:


https://git.tizen.org/cgit




thanks
- jf.ding



On Monday, March 9, 2015 at 2:58 PM, Jing Yang wrote:

Hi,


I tried to build IVI branch according to page: 
https://source.tizen.org/documentation/developer-guide/all-one-instructions/creating-tizen-ivi-images-based-on-specific-snapshot-one-page
By default, the example in this page is for x86. I did some modification based 
on the example command: using the arm based snapshot manifest, and download arm 
based pre-builts binaries and build-config.
I tried many times, but it always fails to download prebuild binaries. 


Did someone succedd to build ivi according to this guide?


Thanks


Jing Yang



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

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

Reply via email to