similar to: [LLVMdev] llvmc Problems

On Sun, 2006-08-13 at 21:18 +0200, Bram Adams wrote: > Hi, > > Apparently there are two bugs in tools/llvmc/c: This tool is, as yet, unfinished. > > /.../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

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:

Bram Adams wrote: > Hi, > > Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven: > >> >>> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful >>> variable by the llvmc configuration parser. >> >> >> Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around line >> 304. Also, they are recognized

Hi, Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven: > >> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful >> variable by the llvmc configuration parser. > > Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around > line > 304. Also, they are recognized by the lexer. Its more likely that when > you configured LLVM

The utils/NewNightlyTest.pl script seems to use LLVMGCCDIR in a way that is inconsistent with the top-level configure script. I would like to fix this but I don't want to break everyone's nightly tests. Can someone review the attached patch to make sure I'm not missing something? The NewNightlyTest.pl script checks the LLVMGCCDIR environment variable and uses it for two

On Aug 24, 2007, at 1:52 PM, Holger Schurig wrote: > Is llvmc meant for compilation? > I'm not sure what the status of llvmc is (is anyone working on it?), but I don't believe it was ready for real use or was finished. If you would like to work on it, patches are welcomed! Thanks, Tanya > $ llvmc -c a.c -o a.o > /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output

Is llvmc meant for compilation? $ llvmc -c a.c -o a.o /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output type value /usr/src/llvm/dist/etc/llvm/c had 1 errors. Terminating. The offending line contains: optimizer.output = bytecode which doesn't seem to be understood by llvmc. If I uncomment this line, I get another error message: $ llvmc -c a.c -o a.o llvmc: Can't find program

On Sat, 21 Aug 2004 18:36:08 -0500 Misha Brukman <brukman at uiuc.edu> wrote: > On Sat, Aug 21, 2004 at 04:15:49PM -0700, Jeff Cohen wrote: > > I don't know if it's under cvs. It's the "getting started" page > > (http://llvm.cs.uiuc.edu/docs/GettingStarted.html) in section > > "Getting Started Quickly (A Summary)". But careful reading

On Feb 19, 2005, at 20:26, Reid Spencer wrote: > You need to tell configure where the install directory for all of > llvm-gcc is located. Ah ha. That was my problem. I forgot that I ran into this with LLVM 1.4 as well. Basically, I specified: --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin instead of: --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc Which

Hi all I want to cross compile llvm for arm architecture on Devkit8000. ARM toolchain: arm-2011.03 LLVM: llvm-2.9 binutils: binutils-2.21 The following is my approach: 1. install binutils- 2.21 put binutils to llvm src directory ./configure --target=arm-linux

Evan, You need to tell configure where the install directory for all of llvm-gcc is located. When you configured llvm-gcc you provided a --prefix option to the configure script. The value of that option (location of where to install llvm-gcc) is what you need to provide to --with-llvmgccdir= when configuring LLVM. You should follow the instructions in the CFEBuildInstrs.html document:

Hi all LLVM CVS users, Recently, the LLVM makefiles have changed how runtime libraries are handled for the C/C++ frontend. Please take the following steps (assuming 'llvmgccdir' is whatever you normally pass to configure as the --with-llvmgcdir option): 1. Go into your llvm/runtime directory, and run 'make install-bytecode'. This will install runtime libraries into

---------- Forwarded message ---------- From: Qingan Li <ww345ww at gmail.com> Date: 2011/1/19 Subject: Re: [LLVMdev] About test suits Cont1 To: Eric Christopher <echristo at apple.com> *I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application

*I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application programs* (2) tar xzf llvm-2.8.tgz; * // now, the top directory of source tree is /home/qali/llvm-2.8* (3) cd llvm-2.8/projects (4) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

cvs co llvm ... cd llvm; ./configure --with-llvmgccdir=<llvmgccdir>; make ... Compiling llvmAsmParser.cpp Linking /home/dcrowe/llvm/llvmcvs/llvm/lib/Debug/asmparser.o make[2]: Leaving directory `/home/dcrowe/llvm/llvmcvs/llvm/lib/AsmParser' make[2]: Entering directory `/home/dcrowe/llvm/llvmcvs/llvm/lib/Bytecode' make[2]: *** No rule to make target `all'. Stop. make[2]:

Hi Tobias, > I committed an extended version of that patch to llvm core and the test suite. > Can you have a look, if it works for you. if I configure like this then the configure script thinks llvm-gcc is not dragonegg: configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" --with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so" There are several reasons for

Hello; I am still having problems making the llvm-test suite and running command like "make TEST=libcalls report" is giving me unexpected output. So first I tried the following - 1. I built and installed llvm(3.0) under Ubuntu 11.10 (using the ./configure script found under llvm source, and then make and make install). While configuring, I gave --prefix as a directory where I would

On Sat, Aug 21, 2004 at 04:15:49PM -0700, Jeff Cohen wrote: > I don't know if it's under cvs. It's the "getting started" page > (http://llvm.cs.uiuc.edu/docs/GettingStarted.html) in section "Getting > Started Quickly (A Summary)". But careful reading of the remainder of > the page does give the correct path. http://llvm.cs.uiuc.edu/docs/* is a copy of

On Sun, 12 Dec 2004, Reid Spencer wrote: > Hello, > > I need to solicit your opinion about something. > > I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right > now the linkers will use this environment variable if it specifies a > single directory. It will look in that directory to find libraries when > things like -lc or -lcrtend are specified on

LLVMers, If you're not working from the CVS "head", you can ignore this. Otherwise, please read it! I have committed changes to CVS head that require changes to your build environment. This is part of PR432. The changes involve getting the CFE to build an executable named llvm-gcc instead of gcc. The hyphenated name was chosen to be consistent with other LLVM tools, it is also