[LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose
Mikael Lyngvig
mikael at lyngvig.org
Sun Nov 17 01:41:33 PST 2013
FYI: I did decide to go ahead and convert the document. It took about 45
minutes, so it wasn't too bad - this even includes a few rewrites so that
it is no longer a personal tale of MY adventures with LLVM, but rather a
fairly decent user guide.
I've attached the converted version, but this is not a commit proposal. I
still need to link into Zorg and to document that process. I'll submit it
as a commit request in a week or so - when my two new builders have proved
themselves okay. So, you might as well just ignore the attachment :-)
2013/11/17 Sean Silva <chisophugis at gmail.com>
>
>
>
> On Sun, Nov 17, 2013 at 12:53 AM, Mikael Lyngvig <mikael at lyngvig.org>wrote:
>
>> Thanks for spotting those errors! Fixed.
>>
>> If you feel that this doc should be part of the LLVM documentation,
>> perhaps in a revised form, just let me know. I am willing to convert it
>> into reST and also to go through a peer review, but I simply cannot spend
>> hundreds of hours munging about, rewriting, and retesting over and over as
>> I am already busy on other documentation and other sub-projects.
>>
>
> If it would require a format conversion, it's not a big deal. However, it
> would be nice to add a link to an appropriate document. Probably just tack
> it on at the end of HowToBuildOnARM (which should be called
> AgglomerationOfTipsForBuildingOnARM) with a sentence of description.
>
> -- Sean Silva
>
>
>>
>> -- Mikael
>>
>>
>> 2013/11/17 Dmitri Gribenko <gribozavr at gmail.com>
>>
>>> On Sat, Nov 16, 2013 at 9:15 PM, Mikael Lyngvig <mikael at lyngvig.org>
>>> wrote:
>>> >
>>> http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM
>>>
>>> > Notice: You only need Ninja for the test build; none of the official
>>> LLVM builders use Ninja as far as I know.
>>>
>>> My buildbots use ninja.
>>>
>>> > Please notice that you must specify the absolute path to ninja,
>>> otherwise CMake can't figure out where it is located.
>>>
>>> Strange, I never had to do this. I just put 'ninja' binary into my PATH.
>>>
>>> > pushd llvm-trunk/tools > /dev/null
>>>
>>> This does not look correct to me, because you are not entering the
>>> 'clang' directory. Similarly, for compiler-rt below.
>>>
>>> Dmitri
>>>
>>> --
>>> main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
>>> (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131117/61263f6d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: HowToSetupAnArchLinuxBuildbot.rst
Type: application/octet-stream
Size: 16960 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131117/61263f6d/attachment.obj>
More information about the llvm-dev
mailing list