similar to: [LLVMdev] Windows build broken?

steve naroff <snaroff at apple.com> writes: > Folks, > > It appears the Windows build has regressed over the past week. > > The build fails quite early (during the "Performing TableGenStep" > phase). > > Any help/pointers would be appreciated. It breaks for me because the usage of INT64_C, which was introduced on r57663 and 57668. Some googling around

Óscar Fuentes <ofv at wanadoo.es> writes: >> It appears the Windows build has regressed over the past week. >> >> The build fails quite early (during the "Performing TableGenStep" >> phase). >> >> Any help/pointers would be appreciated. > > It breaks for me because the usage of INT64_C, which was introduced on > r57663 and 57668. >

I have updated "DataTypes.h.in", could you do a svn update and see if it works ? -Argiris Óscar Fuentes wrote: > Óscar Fuentes <ofv at wanadoo.es> writes: > > >>> It appears the Windows build has regressed over the past week. >>> >>> The build fails quite early (during the "Performing TableGenStep" >>> phase).

Folks, Is anyone still using the Visual Studio solution files in the win32 directory? If they aren't being maintained, they should probably be removed (to avoid any confusion). Thanks for any feedback, snaroff

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'm seeing the following build problem on Windows. I'm using cmake, but haven't verified "it" is the problem. Is anyone else seeing this problem? Any help would be appreciated. Thanks, snaroff -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 21.png Type: image/png Size: 24840 bytes Desc: not available URL:

Hi Oscar, For development, CMake is working great for me. I rarely get build errors related to the project file being out-of-date. Is it true that CMake only generates absolute paths? Any idea on the difficulty of generating relative paths? I consider this a pretty big obstacle... Thanks for all your hard work on this, snaroff On Jan 15, 2009, at 9:46 AM, Óscar Fuentes wrote: >

Hello Steve. steve naroff <snaroff at apple.com> writes: > For development, CMake is working great for me. I rarely get build > errors related to the project file being out-of-date. > > Is it true that CMake only generates absolute paths? Any idea on the > difficulty of generating relative paths? I consider this a pretty big > obstacle... Well, the fact that you

On Jan 15, 2009, at 11:40 AM, Óscar Fuentes wrote: > Hello Steve. > > steve naroff <snaroff at apple.com> writes: > >> For development, CMake is working great for me. I rarely get build >> errors related to the project file being out-of-date. >> >> Is it true that CMake only generates absolute paths? Any idea on the >> difficulty of generating

Hi Steve, The Visual Studio solution and project files are quite handy. CMake creates absolute paths instead of relative paths, making it cumbersome to move things around. Also, for newcomers (e.g. students) it's really great to be able to download the package, open the solution and compile without any complication. They haven't been updated in a while, but it would be nice to have

steve naroff <snaroff at apple.com> writes: > I'm seeing the following build problem on Windows. I'm using cmake, > but haven't verified "it" is the problem. > > Is anyone else seeing this problem? > > Any help would be appreciated. Thanks, Those are the same errors reported by OvermindDL1 a few hours ago on this mailing list. I don't think

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 Piortr, This also breaks the hand-built VC++ project. Any clues on where I should define this? Thanks, snaroff -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 7.png Type: image/png Size: 13645 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090202/eb726ff5/attachment.png> -------------- next part

2009/1/28 Mike Stump <mrs at apple.com>: > Author: mrs > Date: Tue Jan 27 20:43:35 2009 > New Revision: 63168 > > URL: http://llvm.org/viewvc/llvm-project?rev=63168&view=rev > Log: > Add a preliminary version number. > > Modified: > cfe/trunk/Driver/clang.cpp > > Modified: cfe/trunk/Driver/clang.cpp > URL:

Folks, I'm having a bizarre build failure on Windows (having to do with basic types such as uint8_t, uint32_t). I've done a clean build and it doesn't seem to fix the problem (I made sure DataTypes.h was removed and regenerated). I searched through the recent llvm commits and can't find anything relevant to this file or data type. If you build llvm on Windows, please let

Looks like your make/install is incomplete wrt clang. I follow the instuctions for checking out the sources but build using cmake instead of configure: > cmake -G ""Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE="Release" -DCMAKE_INSTALL_PREFIX="../bin" ../llvm > make install This builds and installs llvm+clang in the bin

Hi Ashok, I created a new Ubuntu 12.04 virtual machine and followed directions except that I know use your cmake command instead of configure, and I got the error below. Any help is very much appreciated. $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/ tutorial1.cpp In file included from tutorial1.cpp:5: In file included from /home/ubuntu/bin/include/llvm/Support/raw_ostream.h:17:

Add -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS to your compilation flag. On 7/10/2012 11:23 AM, NY Knicks Fan wrote: > Hi Ashok, > > I created a new Ubuntu 12.04 virtual machine and followed directions > except that I know use your cmake command instead of configure, and I > got the error below. > > Any help is very much appreciated. > > > $

On 3/4/20 9:17 AM, Richard W.M. Jones wrote: > Plugins and filters may call this to initiate an asynchronous shutdown > of the server. This would only be used in the connected phase — > plugins should still call exit(3) directly for configuration failure. > > It is equivalent to sending a kill signal to self, but it's cleaner to > have an API for this and better for