similar to: [LLVMdev] LLVMdev Digest, Vol 61, Issue 25

Hello, Lance >Your comment regarding gnuwin32 not being needed is interesting - >I actually installed gnu bison/flex to get past an earlier crash in >configure. Which version of LLVM you're building? > (c:/mingw/bin/../lib/gcc/mingw32/4.3.3/../../../../mingw32/bin/ld.ex mingw32 gcc 4.x should be considered as 'alpha'. 3.4.5 is known to be stable. This might give you the

I am just beginning to use LLVM, and find that 'getting started' is the steep part of the learning curve. I am using MingW and msys, which I have not fully grokked yet. Anyway, actually building the libraries from source is turning out to be difficult. I want to work with LLVM as described in the except from the LLVM FAQ below. I am using C++, so the FFI is a non-issue. Can someone

Hi John, I have attached my Makefile.config. I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables defined as such in my environment. But I noticed that this is defined in the Makefile.config by default to the same values. All the same, I tried defining both these variables in my .cshrc, but I still get the same error. The main directory for me is /home/llvm, and I have

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

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

By the way, somebody (I think it was Chuck, but I don't remember for certain) was asking for the BuildLog.htm from building the llvm.sln file under VS 2005 SP1 for diagnostic purposes; right now the SLN is configured to produce a new BuildLog for each and every one of the projects inside the solution. I don't know who's responsible for this guy, but that's probably not the best way

>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

>There's a config.h file in the win32 subdirectory that implies that it's >supposed to be concatenated as part of the build process, but it doesn't >seem like that's happening from within the .sln script--am I missing a >pre-build step someplace? When config.h.in is hit in the build of configure the configure project, the configure.h file from the win32 directory is

yue wrote: > hi, > about [LLVMdev] another question > > thanks > > yueqiang One other thing you might want to try is to put your object tree in a directory that is *not* inside of your source tree. Currently, we don't support using separate object trees that are subdirectories of the source tree. In other words: Will work: ========== SRC_ROOT=/home/yue/llvm

More on this: Walking through the projects slowly: (*) "Configure" builds with no problem. (*) "support" fails: C:\Prg\llvm-2.2\llvm-2.2\win32>msbuild llvm.sln /t:Build Microsoft (R) Build Engine Version 2.0.50727.1433 [Microsoft .NET Framework, Version 2.0.50727.1433] Copyright (C) Microsoft Corporation 2005. All rights reserved. Build started 2/18/2008 12:07:45 AM.

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

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

Hello, Ted. > (*) build LLVM itself > (*) build programs with LLVM > > I have a MingW32 setup on a WinXP machine; You can see http://wiki.llvm.org/index.php/Notes:MingW32 to get instructions how to build LLVM on mingw32 box. For building programs with LLVM itself you'll probably need llvm-gcc4, which you can either compiled by yourself (tricky on mingw32) or use prebuilt one in

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