similar to: [LLVMdev] Installation problem

Hi, It looks like the permissions aren't set for read access for non-root users. The command for fixing that is "chmod". If you look up chmod in the man pages of the Ubuntu help files it should give instructions on how to use it. I hope this helps, --Sam --- On Mon, 8/25/08, August Karlstrom <fusionfile at comhem.se> wrote: > From: August Karlstrom <fusionfile at

Hi, After building llvm with clang the llvmc tests are failing with: llvmc: Node llc is not in graph Anyone else see this ? (TOT llvm & clang) -Argiris

Hi, I built LLVM + Clang on Mac OS X and ran make check. I get the following result summary: Failing Tests (11): LLVM :: LLVMC/C++/dash-x.cpp LLVM :: LLVMC/C++/hello.cpp LLVM :: LLVMC/C++/just-compile.cpp LLVM :: LLVMC/C++/together.cpp LLVM :: LLVMC/C++/unknown_suffix.unk LLVM :: LLVMC/C/hello.c LLVM :: LLVMC/C/opt-test.c LLVM :: LLVMC/C/sink.c LLVM ::

On 08/05/2010 07:54 PM, Daniel Dunbar wrote: > Hi Argyrios, > > This has been happening for a long time, no one has debugged it yet. > > I personally always configure llvm with --without-llvmgcc and > --without-llvmgxx, which disables these tests. I believe the reason is that llvmc is not built at all with the cmake system. Here is the relevant bug report.

Hi, I'm having some problems cross-compiling from ppc (OS X) to x86 object files and to ia64, at all. I'd appreciate some advice as to whether or not I'm actually supposed to be able to do this, and what's wrong if so. Here's how I configured it: ../llvm-darcslocal/llvm/configure --with-llvmgccdir=$LLVMGCCDIR --prefix=$HOME/Documents/hpcl/LLVM/install The results work fine

OK, I noticed a few problems with my previous email, so I will boil the question down: What I want to do is compile for x86 and ia64 from darwin. I also want to load my own passes into opt and llc. Should I be using llvmc at all here, or should I be doing something like llvmgcc -> gccas -> opt -> llc ? I've given up on the filetype=obj argument, so now the problem is that llc is

Hi I have a few problems installing/updating packages with complicated dependencies. For example, the Rmpi package: update.packages(...) checking for mpi.h... no configure: error: "Cannot find mpi.h header file" ERROR: configuration failed for package ?Rmpi? So I tried: >install.packages("Rmpi",configure.args="--with-mpi=/usr/lib/openmpi") Trying to find

Hi! I'm trying to do a lm() test on three objects. My problem is that R protests and says that the variable lengths differ for one of the objects (Sweden.GDP.gap). But I have double checked that the number of observations are the same. All three objects should contain 9 observations but R only accepts 9 observations in two of the objects. The third must have 10! Very confusing because there

Hi I get the following warings on my ubuntu (gutsy) machine > library(matrix) > data.frame(x=1:5, z=5)[1:5, ] x z 1 1 5 2 2 5 3 3 5 4 4 5 5 5 5 Warning message: ':::' is deprecated. 'methods' is deprecated. 'seemsS4Object' is deprecated. Use 'isS4' instead. See help("Deprecated") It is quite annoying since I often subset the data.frames. Will

On 11/08/2010 03:18 PM, Duncan Sands wrote: > Hi Tobias, > >> I am very interested in using dragonegg as a fortran frontend for the >> LLVM test >> suite, as a start to improve fortran support. >> >> I believe this should be easy, but when I looked into this I had the >> impression >> the nightly tester in the llvm test-suite does not even support

On Wed, 28 Jul 2004, Reid Spencer wrote: > 2. MODE OF OPERATION > ==================== > The driver will simply read its command line arguments, read its > configuration data, and invoke the compilation, linking, and > optimization tools necessary to complete the user's request. Its basic I'm not sure that I agree with this. Compilers need to be extremely predictable and

I am getting this error while using the command "llvmc -O3 -Wall hello.cpp" where hello.cpp is some cpp file on my machine. llvmc is the driver calling a bunch of tools like llvm-g++, opt, llc etc. I think the llvmc tool could not probably locate the llvm-g++ tool. I would like to know where should I specify the path to llvm-g++ for llvmc to find them. Also can someone give me the link

I'm seeing this new build failure, starting some time yesterday on ARM: make[3]: Entering directory `/home/nlewycky/llvm/tools/llvmc/driver' llvm[3]: Linking Debug executable llvmc g++ -DLLVMC_BUILTIN_PLUGIN_1=Base -DLLVMC_BUILTIN_PLUGIN_2=Clang -I/home/nlewycky/llvm/include -I/home/nlewycky/llvm/tools/llvmc/driver -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g

Dear llvm, I just tried to compile a simple file hello.c. But each time I used llvmgcc hello.c, it gave me the following error: xli3|csil-suna33|~/cs426|[13]% llvmgcc hello.c as: error opening '/var/tmp//ccapglpE.o': file exists! Use -f command line argument to force output I really got confused. Could you please let me know what's wrong? thanks, Jerry

LLVMers, As part of my work on bug 353: Create Front End Framework And Compiler Driver (http://llvm.cs.uiuc.edu/PR353), I'm starting a discussion on the design and requirements of the compiler driver. If you have comments on this, by all means PLEASE chime in. This is by no means cast in stone. The results of the ensuing discussion will be documented in PR353 (and elsewhere) and I'll use

Thanks, Chris, Below is the output of 'llvmgcc he.c -v' xli3|csil-suna27|~/cs426|[35]% llvmgcc he.c -v Reading specs from /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-lib/llvm/3.1/specs Configured with: /home/vadve/lattner/cvs/gcc/configure --srcdir=/home/vadve/lattner/cvs/gcc --prefix=/home/vadve/lattner/cvs/gcc_install_sparc --target=llvm --enable-languages=c

On Sun, Sep 4, 2011 at 8:40 PM, S. Bharadwaj Yadavalli <bharadwajy at gmail.com> wrote: > Hi, > > I built LLVM + Clang on Mac OS X and ran make check. I get the > following result summary: > > Failing Tests (11): >    LLVM :: LLVMC/C++/dash-x.cpp >    LLVM :: LLVMC/C++/hello.cpp >    LLVM :: LLVMC/C++/just-compile.cpp >    LLVM :: LLVMC/C++/together.cpp >  

Hi, Apparently there are two bugs in tools/llvmc/c: /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item /.../llvm/tools/llvmc/c:28: Error: Expecting a program name /.../llvm/tools/llvmc/c had 2 errors. Terminating. The first error relates to the following line(s): lang.libs=%llvmgccdir%/lib %llvmgccdir%/lib \ %llvmgccdir%/lib/gcc/%llvmgccarch% ... the other one to:

On Wed, 2004-07-28 at 11:26, Chris Lattner wrote: > On Wed, 28 Jul 2004, Reid Spencer wrote: > > 2. MODE OF OPERATION > > ==================== > > The driver will simply read its command line arguments, read its > > configuration data, and invoke the compilation, linking, and > > optimization tools necessary to complete the user's request. Its basic > >

On Fri, Oct 29, 2010 at 11:14 PM, Chris Lattner <clattner at apple.com> wrote: > > On Oct 29, 2010, at 10:21 PM, Xinliang David Li wrote: > > > > 2010/10/29 Rafael Espíndola <rafael.espindola at gmail.com> > >> > clang -x c foo.c -emit-llvm-bc -o /tmp/llvm_JnS1o8/foo.bc >> > (.text+0x20): undefined reference to `main' >> > collect2: