search for: fileparser

...pp for Release build llvm[2]: Compiling CallingConvEmitter.cpp for Release build llvm[2]: Compiling CodeEmitterGen.cpp for Release build llvm[2]: Compiling CodeGenTarget.cpp for Release build llvm[2]: Compiling DAGISelEmitter.cpp for Release build llvm[2]: Flexing FileLexer.l llvm[2]: Bison of FileParser.y SKIPPED -- bison not found llvm[2]: Compiling FileLexer.cpp for Release build /usr/home/emil/llvm-2.0/utils/TableGen/FileLexer.l:34:24: FileParser.h: No such file or directory Is this a packaging issue where FileParser.h was omitted from the tarball, or does LLVM *need* bison in order to build?...

...the same as linux and > started the build. We'll see if the two are similar enough for it to > work. The change caused the first error to become: > > test: Linux: bad number This isn't my day... gmake[2]: Entering directory `/usr/home/llvm/obj/utils/TableGen' Bisoning FileParser.y Flexing /usr/home/llvm/obj/../utils/TableGen/FileLexer.l gmake[2]: Leaving directory `/usr/home/llvm/obj/utils/TableGen' gmake[2]: Entering directory `/usr/home/llvm/obj/utils/TableGen' Compiling AsmWriterEmitter.cpp Compiling CodeEmitterGen.cpp Compiling CodeGenTarget.cpp Compiling FileL...

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 30 Aug 2004 21:46:42 -0700 >FileParser.tab.c: In function `int Fileparse()': >FileParser.tab.c:2043: error: syntax error before `goto' > >The offending lines bison generated are: > >/*----------------------------------------------------. >| yyerrlab1 -- error raised explicitly by an action. | >`------------...

...iled the llvm-1.9. Can you please send me the correct source code. I am getting the following errors when I compiled the llvm-1.9 on linux-ubuntu with the following command. make -k | tee gnumake.out ENABLE_OPTIMIZED=1 /home/baburao/Desktop/LLVM/llvm-1.9/utils/TableGen/FileLexer.l:33:24: error: FileParser.h: No such file or directory /home/baburao/Desktop/LLVM/llvm-1.9/utils/TableGen/FileLexer.l:186: error: 'Filelval' was not declared in this scope /home/baburao/Desktop/LLVM/llvm-1.9/utils/TableGen/FileLexer.l:187: error: 'CODEFRAGMENT' was not declared in this scppe. g++: /home/ba...

> llvm[2]: Flexing FileLexer.l > llvm[2]: Bison of FileParser.y SKIPPED -- bison not found > llvm[2]: Compiling FileLexer.cpp for Release build > /usr/home/emil/llvm-2.0/utils/TableGen/FileLexer.l:34:24: FileParser.h: No such file or directory > > Is this a packaging issue where FileParser.h was omitted > from the tarball, or does LLVM *need* b...

On Mon, 17 Sep 2007, Emil Mikulic wrote: >> The 2.1 pre-release (version 1) is available for testing: >> http://llvm.org/prereleases/2.1/version1/ > > I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be > stale. I tried building LLVM without bison installed and got: Can you try it again without bison with these files: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070917/053582.html If they work, we should merge them into 2.1. Thanks Emil! -Chris...

On Mon, 2004-08-30 at 21:46, Jeff Cohen wrote: > This isn't my day... > > gmake[2]: Entering directory `/usr/home/llvm/obj/utils/TableGen' > Bisoning FileParser.y > Flexing /usr/home/llvm/obj/../utils/TableGen/FileLexer.l > gmake[2]: Leaving directory `/usr/home/llvm/obj/utils/TableGen' > gmake[2]: Entering directory `/usr/home/llvm/obj/utils/TableGen' > Compiling AsmWriterEmitter.cpp > Compiling CodeEmitterGen.cpp > Compiling Cod...

On Fri, Sep 14, 2007 at 11:42:18PM -0700, Tanya Lattner wrote: > LLVMers, > > The 2.1 pre-release (version 1) is available for testing: > http://llvm.org/prereleases/2.1/version1/ I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be stale. I tried building LLVM without bison installed and got: gmake[2]: Entering directory `/home/emil/ll/objdir-llvm/utils/TableGen' llvm[2]: Compiling AsmWriterEmitter.cpp for Release build llvm[2]: Compiling CallingConvEmitter.cpp for Release build llvm[2]: Comp...

On Mon, Sep 17, 2007 at 12:25:40PM -0700, Chris Lattner wrote: > On Mon, 17 Sep 2007, Emil Mikulic wrote: > >> The 2.1 pre-release (version 1) is available for testing: > >> http://llvm.org/prereleases/2.1/version1/ > > > > I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be > > stale. I tried building LLVM without bison installed and got: > > Can you try it again without bison with these files: > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070917/053582.html > > If they work, we should merge them in...

On Mon, 30 Aug 2004 20:48:45 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > When I ran configure after updating, I get various errors. First: > > % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc > checking for a BSD-compatible install... /usr/bin/install -c > checking build system type... i386-unknown-freebsd5.2.1 > checking host system

Good day, After having lurked for a while I''ve decided to actually start using puppet starting on my small home network. I''ve been following : http://reductivelabs.com/trac/puppet/wiki/InstallationGuide and :- http://www.howtoforge.com/installing_puppet_on_ubuntu to test puppet on 2 hosts, librarian running the puppetmasterd and mortvm. Unfortunately, I

I finally succeded in compiling TableGen with Visual Studio. In the end I made normal solution and project files for VS instead of using Paolo's SConstruct based build system because of my lacking familiarity with SConstruct. One of the main obstacles was getting the FileLexer and FileParser to build correctly. First of all the output file for FileLexer is specified with a %option, which is not very convenient because this means I cannot control which directory this file is put in. I had to get rid of this line and specify the output on the command line instead. I imagine this requ...

When I ran configure after updating, I get various errors. First: % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc checking for a BSD-compatible install... /usr/bin/install -c checking build system type... i386-unknown-freebsd5.2.1 checking host system type... i386-unknown-freebsd5.2.1 checking target system type... i386-unknown-freebsd5.2.1 test: Unknown: bad

...MinGW/llvm/utils/TableGen/Debug/AsmWriterEmitter.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/CodeEmitterGen.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/CodeGenTarget.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/FileLexer.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/FileParser.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/InstrInfoEmitter.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/InstrSelectorEmitter.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/Record.o /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/RegisterInfoEmitter.o /C/Projects/build/M...

The $vmdk value is a directory name in ESX.pm, although the later codes replace '/' with '_', the volume name isn't still friendly, for example, it looks like this: # virsh vol-list pool-dir Name Path ----------------------------------------- esx4.1-rhel6.2-x86_64_esx4.1-rhel6.2-x86_64

...Mon, Sep 17, 2007 at 12:25:40PM -0700, Chris Lattner wrote: >> On Mon, 17 Sep 2007, Emil Mikulic wrote: >>>> The 2.1 pre-release (version 1) is available for testing: >>>> http://llvm.org/prereleases/2.1/version1/ >>> >>> I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be >>> stale. I tried building LLVM without bison installed and got: >> >> Can you try it again without bison with these files: >> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- >> Mon-20070917/053582.html >> >> If th...

...leGen/Debug/AsmWriterEmitter.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/CodeEmitterGen.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/CodeGenTarget.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/FileLexer.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/FileParser.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/InstrInfoEmitter.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/InstrSelectorEmitter.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/Record.o > /C/Projects/build/MinGW/llvm/utils/TableGen/Debug/RegisterInfoEmitter.o...

...? llvm/tools/llvm-stub/Depend ? llvm/tools/opt/Debug ? llvm/tools/opt/Depend ? llvm/utils/Burg/Debug ? llvm/utils/Burg/Depend ? llvm/utils/Burg/gram.tab.c ? llvm/utils/Burg/gram.tab.h ? llvm/utils/TableGen/Debug ? llvm/utils/TableGen/Depend ? llvm/utils/TableGen/FileLexer.cpp ? llvm/utils/TableGen/FileParser.cpp ? llvm/utils/TableGen/FileParser.h ? llvm/utils/TableGen/FileParser.output ? llvm/utils/fpcmp/Debug ? llvm/utils/fpcmp/Depend Index: llvm/lib/Transforms/Scalar/LowerGC.cpp =================================================================== RCS file: /var/cvs/llvm/llvm/lib/Transforms/Scalar/Lowe...

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In

...st return a value in order to compile with VS 2005 There's a ton of warnings, a few of which seem to be 'real' but most are just noise - I don't have time to go through them, but I can mail you the build logs if you're really interested. Last there is an annoyance in that the FileParser.y custom build rule doesn't find the output, so it is run every time you build. This wouldn't be so bad if it was only this file, but it in turn causes Intrinsics.gen to be generated every time and this causes a lot of other files to be rebuilt. I hacked the dobison.cmd script so it never...