similar to: fatal error if Flex and Bison is not configured

Hi,   The unstable repository seems to be quite unstable even building the image... !! I see:   make[4]: Entering directory `/foo/xen-unstable.hg/tools/libxl'' gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .xl.o.d  -D_LARGEFILE_SOURCE

Hi,   The unstable repository seems to be quite unstable even building the image... !! I see:   make[4]: Entering directory `/foo/xen-unstable.hg/tools/libxl'' gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .xl.o.d  -D_LARGEFILE_SOURCE

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.

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1280829528 -3600 # Node ID b2ed7cc08554cba162f93cb95e84c2130d76b314 # Parent 8cd4de118ca4d0124011bff1611ddc2e04bd6566 libxl: free values in XLU_ConfigSetting. Fixes these valgrind reported leaks, found with "valgrind xl create -n ..." ==21170== 8 bytes in 3 blocks are definitely lost in loss record 1 of 3

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

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

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

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

# xl cpupool-create ''name="pool2" sched="credit2"'' command line:2: config parsing error near `sched'': syntax error, unexpected IDENT, expecting NEWLINE or '';'' Failed to parse config file: Invalid argument *** glibc detected *** xl: free(): invalid pointer: 0x0000000001a79a10 *** Segmentation fault (core dumped) Looking at the code

flight 12988 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12988/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 4 xen-build fail REGR. vs. 12979 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 12

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

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

I wrote: > Also I wrote: > > However, xl fails on config files which are missing the final > > newline. This should be fixed for 4.2. > > My patch for this didn''t make it into 4.2 RC4. Should this go into 4.2.0 or be held for 4.2.1 (or is it not 4.2.x material at all) ? Ian. From: Ian Jackson <ian.jackson@eu.citrix.com> Subject: [PATCH] libxl: Tolerate xl

So i am getting this cc1: warning: -Wformat-nonliteral ignored without -Wformat [-Wformat-nonliteral] libxlu_cfg_y.c: In function ''xlu__cfg_yyparse'': libxlu_cfg_y.c:1292:41: error: ''scanner'' undeclared (first use in this function) yychar = yylex (&yylval, &yylloc, scanner); ^ libxlu_cfg_y.c:1292:41: note:

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

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 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Should that work,

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 executables in your path. I build with VisualStudio 2k5

>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're on the PATH? When I ran the build from > inside VS, I get some

NSD 4.10.0rc1 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.10.0rc1.tar.gz sha256 ad476e82eee5bdabc985e071cabe6a68263dd02eac6278ce2f81798b8c08f19f pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.0rc1.tar.gz.asc Version 4.10.0 integrates simdzone and drops the Flex+Bison zone parser. NSD used a Flex+Bison based zone parser since version 1.4.0. The parser served NSD well, but zones have

Asterisk has this error on compile: flex ast_expr2.fl "ast_expr2.fl", line 50: unrecognized %option: reentrant "ast_expr2.fl", line 51: unrecognized %option: bison-bridge "ast_expr2.fl", line 52: unrecognized %option: bison-locations make: *** [ast_expr2f.c] Error 1 2.6.12-1.1447_FC4smp #1 SMP bison (GNU Bison) 2.0 Written by Robert Corbett and Richard Stallman.