<div dir="ltr">I finally got it to work - and my ODROID-XU is now a passive member of the LLVM builder society for the next week or so, until it has proven itself (it monitors changes to the SVN repository and builds in my end without bothering anyone at LLVM.org about its findings). I did write up a "short" treatise on how to do it, in case anybody needs to do this sometime in the future. I expect it to be finished with the final steps of how to link into Zorg, once I get that far.<div>
<br></div><div> <a href="http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM">http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM</a></div><div><br></div><div>The trickiest part is that Arch Linux comes with Buildbot v0.8.8 and LLVM uses v0.8.5. So I had to resort to using a virtual environment and install v0.8.5 instead of v0.8.8.</div>
<div><br></div><div>The next two pending projects are:</div><div><br></div><div> 1. To set up my Mac Mini G4 (PowerPC)/Debian to build and test LLD. Several felt that it needed big-endian testing, so that's what that box will do.</div>
<div> 2. To set up my BeagleBone Black to do something useful, whatever that is. Perhaps it can do an LLD build too, as several requested an ARM build/test of LLD.</div><div><br></div><div>-- Mikael</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/11/14 Renato Golin <span dir="ltr"><<a href="mailto:renato.golin@linaro.org" target="_blank">renato.golin@linaro.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 14 November 2013 17:43, Mikael Lyngvig <span dir="ltr"><<a href="mailto:mikael@lyngvig.org" target="_blank">mikael@lyngvig.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Renato, thanks for your elaborate walk-through of the issues with ARM boards. I'm trying to add some of this to the "How to Build on ARM" document and will submit a patch later on.</div>
</blockquote><div><br></div><div>Nice, thanks! That would be great!</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>Unfortunately, my personal budget does not allow me more than a single Odroid XU board for the time being. So I'll have to do with only one board. I happen to have an eMMC card and it is fairly fast.<br>
</div></div></blockquote><div><br></div><div>That's good. Still, I'd have it running locally on your master for a week or so, just to make sure it's stable enough.</div><div><br></div><div>To create a local master you need to read this doc:</div>
<div><br></div><div><a href="https://buildbot.readthedocs.org/en/v0.8.6/manual/installation.html" target="_blank">https://buildbot.readthedocs.org/en/v0.8.6/manual/installation.html</a><br></div><div><br></div><div>And add Zorg to your master. The way I did was to create a master on buildbot's user dir, (buildbot create-master ~/buildmaster/llvm), checkout zorg, symlink the master/builders configs from zorg into the buildmaster dir, symlink the zorg's Python module into /lib/python2.7/whatever (can't remember), and start the master via (buildbot master start).</div>
<div><br></div><div>Then, I'd create two buildslaves on the board, one in ~/localbot and one in ~/buildbot, with the former pointing to your local master and the latter pointing to LLVM's official master, so that it's easy for you to swap. (<a href="http://llvm.org/docs/HowToAddABuilder.html" target="_blank">http://llvm.org/docs/HowToAddABuilder.html</a>)</div>
<div><br></div><div>On the master, I stripped down all builders from the config and only left my own boards, so that I don't clutter the waterfall/builders page.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div></div>
<div>By the way, how do you set the CPU scheduler to "performance" (procfs something?). Just so that it can be added to the docs.<br></div></div></blockquote><div></div></div><div class="gmail_extra"><br></div>
for ((cpu=0; cpu<`grep -c proc /proc/cpuinfo`; cpu++)); do<br></div><div class="gmail_extra">
<div class="gmail_extra"> sudo sudo cpufreq-set -c $cpu -g performance<br></div><div class="gmail_extra">done</div><div><br></div><div>cheers,</div><div>--renato</div></div></div>
</blockquote></div><br></div>