search for: bison

Hi all, At the moment, LLVM includes the .l, .y sources that are compiled by flex and biston via make. This is fine for most unix developers. For windows developers, it's a bit more of a pain to download flex/bison, but is still a one-time thing. However, anyone releasing an llvm frontend will require their users to have flex/bison. Most (but not all) unix boxes have them, but almost no windows boxes have them. This requires either 1) Forcing the user to dowload flex/bison (bad) 2) Distributing flex/bison...

On Mon, 27 Jun 2005, Alexander Friedman wrote: > Hi all, > have flex/bison. Most (but not all) unix boxes have them, but almost > no windows boxes have them. This requires either > > 1) Forcing the user to dowload flex/bison (bad) > 2) Distributing flex/bison with the front-end (not as bad, but a pain) > > 3) or, and this seems like a simple fix, just di...

On 6/29/05, Chris Lattner <sabre at nondot.org> wrote: > On Mon, 27 Jun 2005, Alexander Friedman wrote: > > Hi all, > > have flex/bison. Most (but not all) unix boxes have them, but almost > > no windows boxes have them. This requires either > > > > 1) Forcing the user to dowload flex/bison (bad) > > 2) Distributing flex/bison with the front-end (not as bad, but a pain) > > > > 3) or, and this se...

...(I seem to be having some trouble getting messages to post on the list so I may be duplicating an earlier post. Apologies if this is the case.) I am compiling CVS tip Asterisk on a fresh CentOS 3.4 install. I got this warning: make ast_expr.a make[1]: Entering directory `/usr/src/asterisk' bison -v -d --name-prefix=ast_yy ast_expr.y -o ast_expr.c ================================================================================= NOTE: Using older version of expression parser. To use the newer version, NOTE: upgrade to flex 2.5.31 or higher, which can be found at NOTE: http://sourceforge.net/...

This patchs adds better support for both Flex and Bison, which might be needed to compile libxl. Now configure script sets BISON and FLEX Makefile vars if bison and flex are found, but doesn''t complain if they are not found. Also, added some Makefile soccery to print a nice error message if Bison or Flex are needed but not found. Please run a...

...After running ./configure and make. I got the following fatal error: *libxlu_cfg_y.y:22:26: fatal error: libxlu_cfg_l.h: No such file or directory compilation terminated.* So the original libxlu_cfg_l.h is deleted when making, and should be regenerated but it is not. I find the path of flex and bison is not set. When I add the correct path of flex and bison in tools.mk manually, This error is fixed. So, Is there anything in build scripts to modify to avoid this error ? Regards Wangzhihao _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://l...

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 -- http://nondot.org/sabre/ http://llvm.org/

I want to play around with the GLR support in the recent bison, so I simply fixed the skeleton. On Tue, 31 Aug 2004 07:31:25 -0700 Reid Spencer <reid at x10sys.com> wrote: > On Mon, 2004-08-30 at 21:46, Jeff Cohen wrote: > > I'm using bison 1.875. But it worked the last time, so I don't know why > > it doesn't work now. D...

...n, 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. So far so good. I removed bison and objdir and srcdir, unpacked a fresh...

> If you use bison instead of yacc this bug is not exposed. > > Is this correct behavior? I guess so. bison is quite different to yacc, see "info bison". llvm depends on bison and this is quite well documented. At http://llvm.org/releases/2.3/docs/GettingStarted.html#software it says "bison&q...

I have problems getting the GNU tools to execute properly. I installed bison, sed, and flex from gnuwin32.sourceforge.net as suggested in the README. The installers for these packages did not want to put them in the llvm/win32/{tools,share} directory, which is unfortunately where the project files expect them to be. I copied the files manually to these directories, but bi...

I have flex and bison from Cygwin installed: $ flex --version flex version 2.5.4 $ bison --version bison (GNU Bison) 2.3 Written by Robert Corbett and Richard Stallman. Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for...

More bison woes. llvm-2.1 + the patch Chris mentioned builds without bison, but llvm-gcc4 doesn't: /home/emil/ll/llvm-gcc4.0-2.1.source/missing bison -d -o gengtype-yacc.c ../../llvm-gcc4.0-2.1.source/gcc/gengtype-yacc.y WARNING: `bison' missing on your system. You should only need it if...

...ction was successful based on correlating information between /var/log/secure and /var/log/messages. But I am looking for some suggestions for implementing more preventative measures, if necessary. The log information from the last few attempts are shown below. /var/log/secure Oct 13 00:14:08 Bison xinetd[2232]: START: rsync pid=15306 from=180.97.106.36 Oct 13 01:55:51 Bison xinetd[2232]: START: rsync pid=15343 from=85.25.43.94 Oct 13 23:25:35 Bison xinetd[2232]: START: rsync pid=16548 from=114.119.37.86 /var/log/messages Oct 13 00:14:08 Bison rsyncd[15306]: rsync: unable to open configura...

Hi all, I'm building the LLVM 2.0 pre-release on a brand new FreeBSD 6.2 install. Without the bison package installed, the build breaks: $ tar zxf llvm-2.0.tar.gz $ mkdir objdir $ cd objdir $ ../llvm-2.0/configure $ gmake [...] gmake[2]: Entering directory `/usr/home/emil/objdir/utils/TableGen' llvm[2]: Compiling AsmWriterEmitter.cpp for Release build llvm[2]: Compiling CallingConvEmitter.c...

Thanks for your comment. I also tried for LLVM 2.2 but got the same compilation errors on VS2005. (I didn't modify anything before the compilation) I just wonder if I need bison and flex even just in the case of compiling them on VS2005 without changing anything because the LLVM doc says "If you plan to modify any .y or .l files, you will need to have bison and/or flex installed where Visual Studio can find them. Otherwise, you do not need them and the pre-generated f...

...to compile asterisk with "make clean; make install", it >> runs okay for a bit and then I get the following error: (ignore >> Outlooks insistence at capitalizing the first letters of these >> lines/sentences - it's all >> lowercase) >> >> Bison ast_expr.y --name-prefix=ast_yy -o ast_expr.c >> Ast_expr.y:110: unrecognized: %locations >> Ast_expr.y:110: Skipping to next % >> Ast_expr.y:141: invalid @-construct >> Ast_expr.y:141: $. Is invalid >> [these last two lines repeat iterating the line number (14...

I have always built it with flex and bison installed, though I believe Chris removed our last dependence on flex a little while back, so you may not need that. I'm using bison 2.1 which I got from the getgnuwin32 folks. I imagine that if you have cygwin or the like, you probably already have everything. You will need to have the exec...

>I have flex and bison from Cygwin installed: WinGNU32 Flex and Bison are the ones to use with LLVM and Visual Studio. http://gnuwin32.sourceforge.net/ The LLVM Visual Studio .sln file is for Visual Studio 2003 so will require conversion and some minor modification. Aaron > Should that work, assuming they...

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