search for: llvmgccdir

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

...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: translator.command=%llvmcc1% -quiet %in% -o %out% \ ... Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful variable by the llvmc configuration parser. I found out in tools/ llvmc/Con...

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 does make sense now. For me, the issue was that the directions (http://llvm.cs.uiuc.edu/docs/GettingStarted.html) were slightly misleading. They say: > ◦ --with-llv...

...inished. > > /.../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: > > translator.command=%llvmcc1% -quiet %in% -o %out% \ > ... > Okay. > Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful > variable by the llvmc c...

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

...path is set correctly: rn-spra1c07:~/llvm/llvm ejones$ which llvm-gcc /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-gcc rn-spra1c07:~/llvm/llvm ejones$ which llvm-g++ /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-g++ So LLVM is on my path, and I ran configure with: ./configure --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin When configure runs, it prints this line: checking whether llvm-gcc is sane... no Is this because I need to use the CVS version of llvm-gcc? Or is it a problem with the configure script? The build on my 3 year old powerbook takes a while (30 minu...

...aries when things like -lc or -lcrtend are specified on the command line. Right now, the only known place this is useful to set to is the CFE's install/bytecode-libs directory. However, the configure script can make that path available to us already because LLVM requires configuring with --with-llvmgccdir=... So, it is my understanding that current usage of LLVM_LIB_SEARCH_PATH is redundant with already available information from the configure script. Does anyone put anything *other* than CFE/install/bytecode-libs in their LLVM_LIB_SEARCH_PATH? Does anyone expect it to actually be a colon separated...

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: http://llvm.org/docs/CFEBuildInstrs.html as well as the getting started guide. Say you have a directory named cfrontend and it contains these directories: llvm-gcc build install If you do this: cd...

...-0700 Reid Spencer <reid at x10sys.com> wrote: > Hi Jeff, > > On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote: > > OK. I've built the front end without any heartaches, but I did > > encountered the following glitches: > > > > The documentation of --with-llvmgccdir is a bit ambiguous. I had to > > try several paths before I got the right one. It should state that > > the directory is <path>/cfrontend/<platform>/llvm-gcc. > > Okay, I'm not sure which documentation you're referring to but if > you'd care to submit...

...eate a full > installation on /usr/local. Naturally that failed because I wasn't root > at the time. I wouldn't want it to install there anyway. You should run 'gmake install-bytecode', not 'gmake install' (I'll fix that in the doc). It should install into the $LLVMGCCDIR/bytecode-libs. You specify the llvm-gcc dir with ./configure --with-llvmgccdir=<dir> so that Makefile.config has correct settings. The default is probably /usr/local which is where it wants to install to. > > > I can create a tarbell of the FreeBSD binaries and upload it to &...

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

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 you didn...

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

...something like "__main**"(I cann't remember very clearly). I followed all the install instructions except the installation dir for llvm is /home/my/llvm/llvm-bin/ and llvmgcc dir is /home/my/llvm/llvm/llvm-gcc and the configure option is --prefix=/home/my/llvm/llvm-bin/ --enable-jit --llvmgccdir=/home/my/llvm/llvm/llvm-gcc </pre> </blockquote> <pre wrap=""><!----> Make sure you set your LLVM_LIB_SEARCH_PATH envvar, as specified in the getting started guide: <a class="moz-txt-link-freetext" href="http://llvm.cs.uiuc.edu/docs/Gettin...

Hi, all I want to compile llvm for arm board , running llvm on Devkit8000 cross-compiler : arm-2008q3 (arm-none-linux-gnueabi) below is my configure: ../llvm-2.9/configure --with-llvmgccdir=/home/poki/hybridQ/llvm/llvm-gcc/llvm-gcc-4.2-2.9-i686-linux --enable-optimized --enable-jit --disable-threads --enable-pic --disable-shared...

...sr/local. Naturally that failed because I > > wasn't root at the time. I wouldn't want it to install there > > anyway. > > You should run 'gmake install-bytecode', not 'gmake install' (I'll fix > that in the doc). It should install into the > $LLVMGCCDIR/bytecode-libs. You specify the llvm-gcc dir with > > ./configure --with-llvmgccdir=<dir> > > so that Makefile.config has correct settings. The default is probably > /usr/local which is where it wants to install to. It did copy the bytefiles to $LLVMGCCDIR/bytecode-libs....

...--enable-bindings=none --disable-multilib --disable-bootstrap --with-sysroot=/path/llvm/arms/sys-root --with-binutils-include=/path/llvm/binutils-2.21/include --with-llvmgccdir=/path/llvm/llvm-gcc-4.2 make make install 2.install LLVM ../llvm-2.9/configure --target=arm-none-linux-gnueabi --host=arm-none-linux-gnueabi --pre...

...inked.bc'. Stop. This means that the make call cannot find the llvm-gcc file. If I type llvm-gcc in the terminal I get: llvm-gcc: no input name Now I have tried running make after running the following configurations. in the test-suite folder: 1) ./configure 2) ./configure --with-llvmgccdir=/llvm-4.2-2.4-x86-linux-RHEL4/bin 3) ./configure --with-llvmgccdir=/llvm-4.2-2.4-x86-linux-RHEL4/bin --with-llvmsrc=/llvm 4) ./configure --with-llvmgccdir=/llvm-4.2-2.4-x86-linux-RHEL4/bin --with-llvmobj=/llvm All of which give me the same error... when I went to /llvm and did a: ./c...

...ke -lc or -lcrtend are specified on the command line. Right > now, the only known place this is useful to set to is the CFE's > install/bytecode-libs directory. However, the configure script can make > that path available to us already because LLVM requires configuring with > --with-llvmgccdir=... Actually, LLVM does *not* require the C frontend, but the only tools that use the environment variable are those that are only used by the CFE. > So, it is my understanding that current usage of > LLVM_LIB_SEARCH_PATH is redundant with already available information > from the config...

...ect/test-suite/trunk test-suite* *(3) cd LLVMGCC_DIR; * ***(4) gunzip --stdout llvm-gcc-4.2-version-platform.tar.gz | tar -xvf -* *(5) cd ~/OBJ_DIR/llvm; * *(6) SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols --enable-assertions * --with-llvmgccdir=LLVMGCC_DIR (7) search LLVMCC_EMITIR_FLAG or "cd projects/test-suite" (both failed) *2. Another question* *In the steps above, I omitted the re-configure process in http://llvm.org/docs/TestingGuide.html#testsuiterun **, since I thought I have configured the $LLVM_GCC_DIR before building...