search for: howtobuildonarm

...ty 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...

...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. It's okay with the manual reformatting; it gives my brain a chance to cool off a bit with relaxed...

...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"...

...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. What if we renamed the ARM document to "TipsForBuildingOnARM" instead of "HowToBuildOnARM"? -- 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 t...

...n'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 fil...

I recommend you copy HowToAddABuilder.rst as a template and put everything you want to add in a new file HowToBuildOnARM.rst. Just write up all of the content that you want to add in that document, and then submit a patch to llvm-commits. At that point, we can then discuss where best to put it, or whether the content could be merged with another page. The important thing is writing up all of the content. As Renato Go...

Hi Sean, Currently, I want to make one note for building LLVM/Clang for ARM, and the other one for testing. People who building LLVM/Clang on a ARM board which has no more than 1G memory, should make a swap partition and use gold to avoid oom. The other one is not so obvious. People who want to run test cases on ARM should build LLVM/Clang with "--with-abi=aapcs" option, this is an

...g 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> >...

..."checking build system type... Invalid configuration `arm-linux-androideabi': system `androideabi' not recognized configure: error: /bin/bash autoconf/config.sub arm-linux-androideabi failed" i modified the command available in the following link http://llvm.org/releases/3.3/docs/HowToBuildOnARM.html ./configure --build=armv7l-unknown-linux-gnueabihf \ --host=armv7l-unknown-linux-gnueabihf \ --target=armv7l-unknown-linux-gnueabihf --with-cpu=cortex-a9 \ --with-float=hard --with-abi=aapcs-vfp --with-fpu=neon \ --enable-targets=arm --enable-optimized --enable-assertions can any one help...

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.

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

Hi LLVMDev, Since my last update we’ve landed patches for these issues: * Bug 14200 - -fno-rtti not in cxxflags given by llvm-config * Bug 23746 - test-suite lacks CMake support * Bug 25059 - CMake libllvm.so.$MAJOR.$MINOR shared object name not compatible with ldconfig On my last thread Jonathan Roelofs pointed out that there is a workaround for Bug 21568 (Cannot add rpath), so I’m making it