similar to: [LLVMdev] Recompiling llvm+clang how-to?

Hi Journeyer J. Joh, > I have questions about compiling Clang+llvm. > > I compile as the link below instructs. > > http://clang.llvm.org/get_started.html > > I do on Ubuntu 12.04. > > `time make -j5` prints for about 13 minutes to compile a brand new > version of Clang+llvm. > And after this I edit some C++ code(clang/tools/driver/driver.cpp) and > compiles

Hello Mr. Ciao and people on our list I tried this last night and now in the morning I captured the problem status. Could you please advise me on this problem? - I downloaded brand new clang+llvm and compiled it as instructed from the url below. >> http://clang.llvm.org/get_started.html - I added some code to tools/clang/tools/driver/driver.cpp 343 int main(int argc_, const char **argv_)

Hello, Thank you for your kind attention to my issue and your help. I changed the tool chain and tried again. And there is a little progress but still have some problem. Using --sysroot doesn't make clang use linker(ld) in the cross tool. Most important question is how I can make clang use cross tool linker. Let me show you my experiment and questions below. There are two questions. [Run]

Hello Gergö, Joerg and people on our list With your kind answer, I tried to build a hello world program for ARM(arm-none-linux-gnueabi) on my x86-64 PC. Thank you we verified the generated bitcode. The only thing remained is linking. Let me brief what I did so far. 1. Built Clang/llvm in a way explained in http://clang.llvm.org/get_started.html on Ubuntu 11.10 x86-64 PC 2. Downloaded gcc-4.0

Hello > ./clang -v -emit-llvm -ccc-host-triple arm-none-linux-gnueabi > -I/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/include > -L/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin hello.c You forgot about sysroot here. > /home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin/ld: > unrecognised emulation mode: armelf_linux_eabi >

Hi Joerg, Thank you very much! I finally found a working command string to cross-compile for ARM on x86. ./clang -v --save-temps -ccc-host-triple arm-none-linux-gnueabi --sysroot=/home/hum/Documents/Projects/arm_toolchain/arm-2010.09/arm-none-linux-gnueabi/libc -gcc-toolchain /home/hum/Documents/Projects/arm_toolchain/arm-2010.09 hello.c -o hello Above works fine! Important options are

Hello list, I wonder if llvm/Clang can compile C or C++ for ARM from on x86. http://comments.gmane.org/gmane.comp.compilers.clang.devel/8896 The talk above answered 'NO' to my question, which means Clang is not yet able to cross compile for ARM on X86. Is the answer still correct for my question? I saw somewhere that Clang supports ARM on Darwin only. Then is the cross compiling

Hello, With your kind concern and help, I now can make a binary for ARM target. ./clang -v --save-temps -ccc-host-triple arm-none-linux-gnueabi --sysroot=/home/hum/Documents/Projects/arm_toolchain/arm-2010.09/arm-none-linux-gnueabi/libc -gcc-toolchain /home/hum/Documents/Projects/arm_toolchain/arm-2010.09 hello.c -o hello The build command is shown above. After that, I prepared an ARM laptop,

On Sat, Jun 16, 2012 at 08:20:23PM +0900, Journeyer J. Joh wrote: > If the cross compiling is supported, is there any documentation on how to > do it? The short version is: assuming you have a cross-binutils installation using e.g. x86_64--netbsd-as and x86_64--netbsd-ld, you add a symlink called x86_64--netbsd-clang to clang and just call that with an appropiate --sysroot to make it find

On 06/27/12 07:24, Journeyer J. Joh wrote: > Hello, > > With your kind concern and help, I now can make a binary for ARM target. > > ./clang -v --save-temps -ccc-host-triple arm-none-linux-gnueabi > --sysroot=/home/hum/Documents/Projects/arm_toolchain/arm-2010.09/arm-none-linux-gnueabi/libc > -gcc-toolchain /home/hum/Documents/Projects/arm_toolchain/arm-2010.09 > hello.c -o

Hello list. I wonder how I can make clang use specific linker. I am now trying to compile a hello world c code on an Ubuntu box for ARM and X86. And I have successfully built for ARM but NOT ABLE TO build one for X86. I am using a cross toolchain in the scratchbox environment of Tizen SDK. You can refer to the url below for my testing environment.

Folks, I realised there's a "checkout_compiler_rt" option on ClangBuilder, which does checkout the sources, but couldn't build them on ARM. I also don't build them during releases (yet) because the configure script doesn't prepare the Makefiles for compiler-rt. A while ago I got it running on ARM with CMake files, but since these are buildbots, I'm not sure

Hi Justin Holewinski, >> As far as I know, there is not a good way to implement user prompts with the LLVM APIs. This info helps me a lot. I tried to do a thing that is not possible. Thank you very much. Sincerely Journeyer 2013/1/15 Justin Holewinski <justin.holewinski at gmail.com>: > Is this for user prompts, or just reading data from stdin? You can use >

And for this kind of question I think I would better hold in. There would be more important issue worth on this list. For this reason I am sorry. Sincerely Journeyer 2013/1/15 Journeyer J. Joh <oosaprogrammer at gmail.com>: > Hi Justin Holewinski, > >>> As far as I know, there is not a good way to implement user prompts with the LLVM APIs. > > This info helps me a

On Sat, Dec 29, 2012 at 9:45 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Klang is tested with LLVM 3.1 > Header file location is often changed. I guess that's why.. I think that klang should be based on the latest SVN/git version of LLVM. -- Sean Silva

Hello, I just applied changes of LLVM 3.2 and it is tested with LLVM 3.2 downloaded from the LLVM Download Page. I just worked for master branch only. The rest of the other branches need to be changed about this also. This will be done as soon as possible. (Before I fix this, If you look at the commits for this issue for master branch, you can easily fix it and test for others also.) Sorry for

Hello list, I use LLVM's vimrc and found that this setting below is useful when editing of reStructuredText file. llvm/utils/vim/vimrc " Enable syntax highlighting for reStructuredText files. To use, copy " rest.vim (http://www.vim.org/scripts/script.php?script_id=973) " to ~/.vim/syntax . augroup filetype au! BufRead,BufNewFile *.rst set filetype=rest augroup END

> I think that klang should be based on the latest SVN/git version of LLVM. OK. I am testing it with LLVM 3.2 wait a minute. -- Journeyer 2012/12/30 Sean Silva <silvas at purdue.edu>: > On Sat, Dec 29, 2012 at 9:45 PM, Journeyer J. Joh > <oosaprogrammer at gmail.com> wrote: >> Klang is tested with LLVM 3.1 >> Header file location is often changed. I guess

Hi, -- Best Regards, Yu Rong Tan

Thanks, Journeyer. I applied the patch with r176235. In future, you can submit patches to the llvm-commits mailing list. :) -bw On Feb 27, 2013, at 9:03 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hello list, > > I use LLVM's vimrc and found that this setting below is useful when > editing of reStructuredText file. > > > llvm/utils/vim/vimrc