The fix for gtest is considered a temporary fix.  Google moved gtest from 
code.google.com to github.com/google.  When it was moved to github, file names 
and code structure was changed just enough that it would no longer build.

By downloading from a mirror that maintained the old code structure we could 
get the build system running again almost instantly.  We still need to update 
the scons scripts to pull the code from github eventually since that is the 
maintained code base.

In the case of boost I would recommend fixing the path, if possible, before 
pulling from a mirror.

George

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Phil Coval
Sent: Monday, November 7, 2016 6:34 AM
To: iotivity-dev at lists.iotivity.org
Cc: aakash.kaushal at legrand.us
Subject: Re: [dev] Req- wiki.iotivity.org/android_build_instructions- Python 
Build error




On 07/11/16 15:25, Aakash KAUSHAL wrote:
Hi Dave,

Greetings !!!

I am working on iotivity and building Iotivity(for Android Platform ) on Ubuntu 
16.0. I am following the steps provide by Iotivity.
https://wiki.iotivity.org/android_build_instructions
(...)


scons: building associated VariantDir targets: out/android/x86/release
scons: *** 
[http://downloads.sourceforge.net/project/boost/boost/1.58.0/boost_1_58_0.zip?r=&ts=1421801329&use_mirror=iweb]
 AttributeError : 'ValueNodeInfo' object has no attribute 'timestamp'


Hi,

Looks the problem source is SF.net backend,

maybe we could replace with this direct link mirror,
like we did for gtest

  *   
http://pkgs.fedoraproject.org/repo/pkgs/boost/boost_1_59_0.tar.bz2/6aa9a5c6a4ca1016edd0ed1178e3cb87/boost_1_59_0.tar.bz2

Does this help?

If yes please drop some notes on

https://wiki.iotivity.org/boost

Thanks



--

mailto:philippe.coval at osg.samsung.com gpg:0x467094BC

https://blogs.s-osg.org/author/pcoval/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161107/656a409a/attachment.html>

Reply via email to