similar to: [LLVMdev] [Patch] Fix dobison.cmd when bison is not found

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 autogen after applying this patch.

Jeff Cohen wrote: > Morten Ofstad wrote: >> Jeff Cohen wrote: >> >>> The recent issues concern the head revision, post 1.9. As no one has >>> ever submitted patches to fix 2005 problems with the 1.9 release, it is >>> safe to say they still exist. >>> >> >> For the 1.5 release I submitted patches that made everything compile

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 distribute the output

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

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

Hi, (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

https://bugzilla.netfilter.org/show_bug.cgi?id=1469 Bug ID: 1469 Summary: Bison reported unused tokens in `nft` Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: nft Assignee: pablo at netfilter.org

I just discovered, by compiling on another machine, that LLVM doesn't compile correctly with *newer* bison versions. The version that I have that works is 1.35. The version that I tried that doesn't work is 1.875. There's a couple bison releases in between those two that may or may not work, I haven't tried them. This isn't really an LLVM problem but it affects LLVM. The

Hi. I had a strange issue today. basically llvm-as refused to do anything, borking out on the simplest of module: ; ModuleID = 'test' @_nothing_works_here = constant i32 42 $ llvm-as test.ll llvm-as: test.ll:1,0: test.ll:1: error: parse error, expecting `GLOBAL' or `CONSTANT' while reading token: '@_nothing_works_here' It turns out that I forgot to install bison before

Hey, everybody--- Ignorance CAN be bliss, at least for a while, but, .... Just so you know... A week or two ago, some upgrades to the expression parser (you know, the expressions you put in $[ ... ] in your extensions.conf file) that I submitted, have been merged into the CVS HEAD of the source. Hopefully, for around 99.9% of you, it won't make any difference to you. The Makefile has also

Hi all, I try to build xen 4.2( revision number: 25161) on Ubuntu 11.10_amd64, Mac pro. 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

To any that may be interested in the implementation of the conditional expression in the expression parser (ast_expr2*) in asterisk, I've filed the patch at: http://bugs.digium.com/view.php?id=4459 Right now, a comment has been added noting that the IF func provides this capability, and asks if both would really be necessary. It's a good question. I haven't been following the

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:

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 you modified a `.y' file. You may need the `Bison' package in order for

Greetings - In my logwatch report this morning I noticed reference to an attempt to connect to rsync from an external IP address. It doesn't appear that the connection 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

> 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" and specifically which version of Bison you've to use.

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. Deleting the __attribute__ clause fixes

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

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

Two suggestions: 1. m4 might be located by your PATH variable. 2. Talk to Morten Ofstad about how he got it to work. Reid. On Wed, 2004-11-03 at 19:34, Jeff Cohen wrote: > 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