similar to: [LLVMdev] compiling release_22 witout bison installed gives broken build

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 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: $ 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,

Folks, Is anyone else the failure below? On Mac OS X everything builds properly... Thanks for any help, snaroff -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 27.png Type: image/png Size: 18959 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081217/e7d37fee/attachment.png>

>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

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.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date]

Oliver Schneider <gmane at assarbad.net> writes: >>> However, we have official git mirrors of most of the projects on >>> llvm.org, would using them instead of svnsync be an option for you? >> >> Well, if the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git

Got it. On Mac OS, the build process update the llvmAsmParser.cpp.cvs file, and then generate llvmAsmParser.cpp from the .cvs file. But on Window, it does not update the .cvs files (probably because bison is missing), and so, the llvmAsmParser.cpp is not in sync with the .y file. As the Mac OS build process update the cvs files, commiting them after building on OS X should be enough to

Sounds like this has to do with Bill backing out r61019, r61030, and r61040. I think 61031 (which update llvmAsmParser.cpp.cvs, etc.) should be backed out as well. Can someone do that? Evan On Dec 17, 2008, at 7:20 AM, Jean-Daniel Dupas wrote: > Got it. > > On Mac OS, the build process update the llvmAsmParser.cpp.cvs file, > and then generate llvmAsmParser.cpp from the .cvs

Hi: I have just started to use llvm and confronted with a problem: when I want to transform something very simple for name.ll to name.bc with llvm-as name.ll, some errors occured: error: parse error, expecting `GLOBAL' or `CONSTANT' while reading token: 'target' btw, the name.ll file is as follows: ; ModuleID = 'tst.bc' target datalayout =

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

For VC++, I solved this by having bison/flex put the files into the obj directories. I also have it unconditionally regenerate the files if bison/flex is available, and copy them from src if they are not. Chris Lattner wrote: > On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote: > >> I can't build LLVM CFE after this patchs >>

>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

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.

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

No solutions come to mind. Conflicts are conflicts and must be resolved manually. This situation should only occur if you change the .l/.y file and then update the .h/.cpp files after someone else has changed the .l/.y file and regenerated the .h and .cpp. That doesn't seem like a high frequency scenario that we need to worry about. Not sure there's much we could do even if it was. Reid.

I created the 1.9 release branch last night. As a reminder, please do not check in any code changes to the release branch. Please send me email if you have changes that need to be merged into the release branch. To check out the release branch: cvs -d <CVS Repository> co -r release_19 llvm cvs -d <CVS Repository> co -r release_19 llvm-test cvs -d <CVS Repository> co -r

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