On Tue, Apr 24, 2012 at 12:08 AM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
On 24 April 2012 10:36, Paul Larson paul.larson@linaro.org wrote:
On Mon, Apr 23, 2012 at 11:55 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 24 April 2012 08:40, Paul Larson paul.larson@linaro.org wrote:
I was trying to run the linaro-android-build-cmds-sh a few times now, and I've never actually been able to get all the way through it. First
time
was due to a lack of space. The drive I tried to run it on had 6G left,
but
apparently that's not enough. So I ran it again on a drive with much more free space. This is running on a core i7, 8GB ram. After 12 hours, I finally got far enough to get an error telling me that vendor.tar.bz2 didn't exist (it did... just not in the path after it did a cd - submitted a small bug for this which should be a very easy fix). So I'm trying again,
but
my question is, should we really be including this test for every build, given that it takes so long to run? How long does this normally take to
run?
Yeah, we should because we should make sure these scripts work. Even your own experience is good.
With a good network connection on my W520 I've seen a build get done in an hour.
Yeah, I don't think it's the build time that's killing me. Not everyone
has
a 50Mb/s connection :)
Hehe...
Andy,
This may be a good thing to put a note in the script about:
- It may take a long time for things to download
- If the script fails in the download - print something out about
starting over. You may want to leave the contents that were already downloaded intact, unless people pass a special flag in).
It already seems to ask/confirm that you want to reuse the existing android directory, which was *really* nice, since it let me continue. So about 12 hours for the download + 2 hours to build and I was finally able to successfully build it using the script.