[LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose

Mikael Lyngvig mikael at lyngvig.org
Sun Nov 17 04:26:42 PST 2013


The great thing about .htaccess is that is user-controlled: You simply put
one in whichever directory you want to use it in.  So no need for a server
admin, unless he/she has specifically disabled it somehow (that I don't
know of).


-- Mikael


2013/11/17 Sean Silva <chisophugis at gmail.com>

>
>
> On Sun, Nov 17, 2013 at 5:36 AM, Mikael Lyngvig <mikael at lyngvig.org>wrote:
>
>> StackOverflows says two things:
>>
>>     1. An example is: <meta http-equiv="refresh" content="0; url=
>> http://example.com/" />.
>>   2. This apparently discouraged by the WWW Consortium who recommends
>> server redirects.
>>
>> It seems that LLVM.org is served by Apache 2.2.22 running on Ubuntu.  In
>> that case, the .htaccess file should make it possible to do server
>> redirects:
>>
>>    RewriteEngine On
>>    RewriteRule /docs/HowToBuildOnARM\.rst
>> http://www.llvm.org/docs/TipsForBuildingOnARM.rst
>>
>> I think that's it.  I use NGINX myself so I can't test it.  I don't think
>> the "http://www.llvm.org" part is necessary.
>>
>
> Yeah, the reason that bug has been open so long is that the "hard" part is
> tracking down the server admin, or otherwise finding a way to get the
> .htaccess file there (may be Sphinx can copy it to the output directory?).
> Then finding some way to reliably test it (or do remote-debugging through
> git/svn).
>
> -- Sean Silva
>
>
>>
>> It's okay with the manual reformatting; it gives my brain a chance to
>> cool off a bit with relaxed stuff in preparation for going to sleep.
>>
>>
>> -- Mikael
>>
>>
>>
>>
>> 2013/11/17 Sean Silva <chisophugis at gmail.com>
>>
>>>
>>>
>>>
>>> On Sun, Nov 17, 2013 at 5:17 AM, Sean Silva <chisophugis at gmail.com>wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Sun, Nov 17, 2013 at 3:50 AM, Mikael Lyngvig <mikael at lyngvig.org>wrote:
>>>>
>>>>> It wouldn't take me more than an hour or two to do the format
>>>>> conversion.  It is rather trivial, actually.  Just say the word and I'm on
>>>>> to it like a starving bee.  I guess I should get used to using the Sphinx
>>>>> layout; I'm simply more familiar with the format I use on my own websites.
>>>>>
>>>>> Have you guys ever considered making a less formal wiki for LLVM
>>>>> documentation - a place where tiny snippets and tricks could be stored?  A
>>>>> place that anybody could contribute to in such a way that only the Wiki
>>>>> editors could accept or reject a proposed change.  Kind of like Wikipedia.
>>>>> http://wiki.llvm.org.  If you are short on resources, I'd be happy to
>>>>> volunteer for the task of co-Wiki-editor (this doesn't require as big
>>>>> knowledge of LLVM as you'd think; it is mostly a matter of rejecting
>>>>> attempts to defame the site and such).  If any topic in the Wiki became too
>>>>> complex or too important, somebody could get started on writing the
>>>>> appropriate coherent, user-friendly documentation that could be merged into
>>>>> the main branch of documents.
>>>>>
>>>>
>>>> Also, I'm not sure how many such "tips and tricks" or "tiny snippets"
>>>> there can be (and I'm cautious about how quickly they will go out of date).
>>>> It's honestly probably easier for LLVM developers to edit files in the
>>>> repository (purely from a workflow perspective).
>>>>
>>>
>>> That "Also," at the beginning was a leftover when I switched the
>>> paragraph order. Please ignore it.
>>>
>>> -- Sean Silva
>>>
>>>
>>>>
>>>> My biggest reason for opposing such a wiki is that it is decoupled from
>>>> the community, which is centered on the mailing lists. A person doesn't
>>>> have to get on the mailing lists to submit an edit to such a wiki, which
>>>> means that they won't become part of the community whereas in order for
>>>> them to contribute to docs/, they have to reach out to the community and
>>>> send a patch, which is a gateway drug to further involvement.
>>>>
>>>>
>>>>
>>>>>
>>>>> What if we renamed the ARM document to "TipsForBuildingOnARM" instead
>>>>> of "HowToBuildOnARM"?
>>>>>
>>>>
>>>> We currently don't have an easy way to serve a redirect to the new
>>>> page, so for the moment we can't rename it (URL's should never break). This
>>>> is <http://llvm.org/bugs/show_bug.cgi?id=14714>. Actually now that I
>>>> think about it maybe we can do it with a dummy html file with a <meta> tag
>>>> with `http-equiv`? Finding a working setup for that is probably a better
>>>> use of your time than reformatting. One other page that is in dire need of
>>>> a rename is clang/docs/Tooling.rst, which is actually "choosing the right
>>>> interface for your application".
>>>>
>>>> -- Sean Silva
>>>>
>>>>
>>>>>
>>>>> -- Mikael
>>>>> -- Apprentice LLVM Tech Writer.
>>>>>
>>>>>
>>>>> 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/8b122d6d/attachment.html>


More information about the llvm-dev mailing list