search for: yacc

...t-prototypes -Wmissing-prototypes -pedantic -Wno-long- long -Wno-variadic-macros -Wno-overlength-strings -Wold-style- definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H - DGENERATOR_FILE -o build/gengtype.exe \ build/gengtype.o build/gengtype-lex.o build/gengtype- yacc.o build/errors.o ../build-i686-pc-cygwin/libiberty/libiberty.a build/gengtype.o: In function `adjust_field_type': /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype.c:763: undefined reference to `_lexer_line' /cygdrive/r/android/llvm/llvm-gcc4.2-o...

...ng-prototypes -pedantic -Wno-long- > long -Wno-variadic-macros -Wno-overlength-strings -Wold-style- > definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H - > DGENERATOR_FILE -o build/gengtype.exe \ > build/gengtype.o build/gengtype-lex.o build/gengtype- > yacc.o build/errors.o ../build-i686-pc-cygwin/libiberty/libiberty.a > build/gengtype.o: In function `adjust_field_type': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:763: undefined reference to > `_lexer_line' > /cygdrive/r/andr...

...>> .depend cc -O -pipe -Wall -D__FBSDID=__RCSID -c /usr/src/games/fortune/strfile/strfile.c cc -O -pipe -Wall -D__FBSDID=__RCSID -static -o strfile strfile.o sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 strfile /usr/obj/usr/src/i386/usr/games echo "===> usr.bin/yacc"; cd /usr/src/usr.bin/yacc; make DIRPRFX=usr.bin/yacc/ obj; make DIRPRFX=usr.bin/yacc/ depend; make DIRPRFX=usr.bin/yacc/ all; make DIRPRFX=usr.bin/yacc/ DESTDIR=/usr/obj/usr/src/i386 install ===> usr.bin/yacc /usr/obj/usr/src/i386/usr/src/usr.bin/yacc created for /usr/src/usr.bin/yacc...

Hi I was interested to see how Mongrel uses Lex/Yacc to parse the HTTP requests using a Regal generated parser. I downloaded the source but do not see the lex and yacc files...

...prototypes -pedantic -Wno-long- > long -Wno-variadic-macros -Wno-overlength-strings -Wold-style- > definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H - > DGENERATOR_FILE -o build/gengtype.exe \ > build/gengtype.o build/gengtype-lex.o build/gengtype- > yacc.o build/errors.o ../build-i686-pc-cygwin/libiberty/libiberty.a > build/gengtype.o: In function `adjust_field_type': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:763: undefined reference to > `_lexer_line' > /cygdrive/r/a...

...7, 17, 4, 5, 9, 18, 19, 22, + 6, 19, 20, 21, 22, 10, 11, 22, 19, 22 }; #define yyerrok (yyerrstatus = 0) @@ -1077,7 +1083,7 @@ yydestruct (yymsg, yytype, yyvaluep, yylocationp, ctx) { free((yyvaluep->string)); }; /* Line 1000 of yacc.c */ -#line 1081 "libxlu_cfg_y.c" +#line 1087 "libxlu_cfg_y.c" break; case 4: /* "STRING" */ @@ -1086,7 +1092,7 @@ yydestruct (yymsg, yytype, yyvaluep, yylocationp, ctx) { free((yyvaluep->string)); }; /* Line 1000 of yacc.c */ -#line 1090 "lib...

...E tarball (731) and managed to get through the ./configure stage, installing rpms as needed. However, when WINE installs it gives me these set of errors: "cd `dirname wrc/__depend__` && make depend make[2]: Entering directory `/mnt/windows/Vault/Wine/wine/wine-20010731/tools/wr c' yacc -bppy -ppp -d -t ./ppy.y make[2]: yacc: Command not found make[2]: *** [ppy.tab.c] Error 127 make[2]: Leaving directory `/mnt/windows/Vault/Wine/wine/wine-20010731/tools/wrc ' make[1]: *** [wrc/__depend__] Error 2 make[1]: Leaving directory `/mnt/windows/Vault/Wine/wine/wine-20010731/tools'...

Hi there!! Can someone tell me where I can find 'supported' lex and yacc utilities that work on NT? Pardon me if this question is not relevant in this list.. Please send me the replies directly to my e-mail 'k.sundram@blr.sni.de' ; since I find that this list is getting bigger and better.. Thanx in advance K R Sundaram -- ************************************...

hello, what about these functions lex/yacc which can parse and recognize a syntax? thanks _____________________________________________________________________________ [[alternative HTML version deleted]]

...kedep -I. -I. -I../../include -I../../include -C. lang.c mcl.c utils.c wmc.c write.c mcy.y -C. make[2]: Leaving directory `/share/Emulators/wine-20010305/tools/wmc' cd `dirname wrc/__depend__` && make depend make[2]: Entering directory `/share/Emulators/wine-20010305/tools/wrc' yacc -bppy -ppp -d -t ./ppy.y make[2]: yacc: Command not found make[2]: *** [ppy.tab.c] Error 127 make[2]: Leaving directory `/share/Emulators/wine-20010305/tools/wrc' make[1]: *** [wrc/__depend__] Error 2 make[1]: Leaving directory `/share/Emulators/wine-20010305/tools' make: *** [tools/__depe...

Hi, On Mon, Jun 16, 2008 at 6:17 PM, Brooks Davis <brooks at freebsd.org> wrote: > LLVM 2.3 is building with no patches and gcc 4.2.1 on FreeBSD OK, so I have taken the changes to BitWriter.cpp from svn and that builds that section of code OK for llvm-2.3. The next part I will need help with, as I dont really know where to start: llvm[3]: Building ARM.td instruction information with

Update to iproute2 is available. Most of the changes were to repair the things that broke with the introduction of the batch mode to the ip command. http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.14-051107.tar.gz For info on CVS ans other info see: http://linux-net.osdl.org/index.php/Iproute2 Masahide NAKAMURA * Updating for 2.6.14 - Show UPD{SA,POLICY} message

# 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

...; This is not a gcc bug, but the assertion failing. A quick diff against > this file shows a huge amount of changes and I have nowhere near > enough knowledge to start comprehending this code. I am only starting > to learn about compilers for my dissertation :) If you use bison instead of yacc this bug is not exposed. Is this correct behavior? -- Best Regards Edd http://students.dec.bournemouth.ac.uk/ebarrett

...-gcc on a x86_64 architecture running a Linux distribution. Using the READM.LLVM I have managed to run ./configure using appropriate options, but when I try to build using make, it shows the following error message after a few seconds: ../../llvm-gcc/gcc/gengtype-lex.l:31:27: fatal error: gengtype-yacc.h: No such file or directory. This happens when trying to build gengtype-lex.c. I could indeed not find the file gengtype-yacc.h in neither llvm-gcc nor llvm code base. Is there a dependency I am missing ? A problem with the configure flags I've used ? Thank you very much in advance for your...

(replying on list in case others are interested, Renato sent me the log offline). Okay, I found problem, the MultiSource/Applications/Burg test is breaking the running of the test suite because it can't find yacc. Can you file a bugzilla for this? We should just add a configure check or something to make sure that doesn't cause the test suite to fall over. You should be able to work around it by installing yacc. - Daniel On Sun, Oct 28, 2012 at 11:27 AM, Daniel Dunbar <daniel.dunbar at gmail.com&g...

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 those modifications to take effect. You can get `Bison' from a...

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

On Oct 28, 2012, at 11:19, Renato Golin <rengolin at systemcall.org> wrote: > On 28 October 2012 17:32, Daniel Dunbar <daniel.dunbar at gmail.com> wrote: >> Exactly how are you running the tests? Via LNT or directly? > > Via LNT, like this: > > ./sandbox/bin/python sandbox/bin/lnt runtest nt \ > --sandbox sandbox \ > --test-suite

...ng a Linux distribution. Using the READM.LLVM I have >> managed to run ./configure using appropriate options, but when I try to >> build using make, it shows the following error message after a few seconds: >> >> ../../llvm-gcc/gcc/gengtype-lex.l:31:27: fatal error: gengtype-yacc.h: No >> such file or directory. >> >> This happens when trying to build gengtype-lex.c. >> >> I could indeed not find the file gengtype-yacc.h in neither llvm-gcc nor >> llvm code base. Is there a dependency I am missing ? A problem with the >> configure f...