similar to: [LLVMdev] Trouble Using scan-build in Windows

I seem to be hitting an error while initializing the scan-build.exe in Windows. C:\Users\lockhaja\llvm\tools\clang\tools\scan-build>perl -S scan-build The getpwuid function is unimplemented at scan-build line 35. Does anyone know what would be causing this error? The perl -S scan-build command appears and runs after I run scan-build from the command prompt. Regards, Jon Lockhart PhD

Hi all, I run a build bot which updates and builds trunk llvm on a variety of OSes once every four hours. The windows build has been broken since r246156: http://104.154.46.123:8010/builders/win-64-trunk. A full clean didn't seem to fix it. Neither did several more recent updates (I'm currently building at 246208). The specific error is at the end of this log:

Here are a couple of representative errors. C:\Dev\upstream\gitmono is where I keep my clone. "C:\Dev\upstream\gitmono\wbuild\ALL_BUILD.vcxproj" (Rebuild target) (1) -> "C:\Dev\upstream\gitmono\wbuild\unittests\Support\DynamicLibrary\SecondLib.vcxproj" (default target) (170:2) -> c1xx : fatal error C1083: Cannot open source file:

msbuild is is able to re-run cmake if a CMakeLists.txt changes. CMake adds a special project "ZERO_CHECK" that does this. However, I am not sure it runs when invoking on the individual projects instead of the solution. Try the cmake --build command, which should output the following: > cmake --build . --target opt CMake is re-running because

I think MSBuild isn't capable of re-running cmake and then reloading the project files when CMakeLists.txt changes. It re-runs cmake, but then continues the build with the stale projects. That probably explains the "PipSqueek.cxx doesn't exist" errors. As for the link error, it could also be caused by things like a file rename not getting picked up by MSBuild. The fix is

I'm trying to get clang 3.6.1 to compile itself on Windows, using this command line: msbuild /p:Configuration=Release /p:CLToolExe=clang-cl.exe /p:CLToolPath=c:\llvm\build\Release\bin\ /p:TrackFileAccess=false /p:Platform="x64" /fileLogger ALL_BUILD.vcxproj It barfed on an occurrence of __try but that was only in a test file so I commented it out and retried. Now it's getting

Different, but still failing (this time with Xcode 4.4…) /Users/rrelph/llvm/tot/xcode/bin/Debug/clang sanitizer_allocator_test.cc.i386.o sanitizer_common_test.cc.i386.o sanitizer_flags_test.cc.i386.o sanitizer_libc_test.cc.i386.o sanitizer_list_test.cc.i386.o sanitizer_printf_test.cc.i386.o sanitizer_stackdepot_test.cc.i386.o sanitizer_test_main.cc.i386.o gtest-all.cc.i386.o

>> Now I'm using LLVM_BUILD_EXAMPLES=OFF and I have >> >> //Build LLVM example programs. >> LLVM_BUILD_EXAMPLES:BOOL=OFF >> >> in the cmakecache.txt file but it also does not seem to >> work. >> > > What that means? LLVM_BUILD_EXAMPLES shall create build targets for the > examples but do not build them when you build the ALL_BUILD

On Sun, Jun 24, 2012 at 1:11 PM, Mason Wheeler <masonwheeler at yahoo.com> wrote: > Hi all, > > I'm trying to build LLVM, synced from SVN trunk yesterday. > > I ran CMake and it generated VS 2008 project files, so far so good.  Then I > tried to build them, by building the ALL_BUILD project. > > It got the first three all right, but choked on template issues in

Hello! I'm wondering whether compiler-rt is expected to be buildable with MSVC 2013. I am currently getting: Error 49 error LNK2005: _free already defined in asan_malloc_win.obj E:\llvm\crt_build\lib\asan\MSVCRT.lib(MSVCR120.dll) Which seems to be the only issue (aside from ~50 warnings, which I'll happily work on cleaning up). I get this when I build the ALL_BUILD project in the

I constructed an LLVM 2.7 VS solution with cmake, but it has 66 projects: ALL_BUILD, ".\ALL_BUILD.vcproj" BrainF, "examples\BrainF\BrainF.vcproj" Fibonacci, "examples\Fibonacci\Fibonacci.vcproj" FileCheck, "utils\FileCheck\FileCheck.vcproj" HowToUseJIT,

>From my own experience this is what I think happens when building the whole solution through Visual Studio's UI. This also happens for building individual projects. I assume something similar happens when building via the command-line, but I rarely do that, so I can't be certain. 1) Visual Studio/MSBuild (I don't know which, but probably MSBuild) determines the dependency graph of

Hello, I'm compiling llvm+clang (both are 3.2) on Windows using CMake + VS2010 (SP1). I have ALL_BUILD successfully passing, but "check-all" fails. Is it expected to pass? Is it expected to pass on Windows with any other toolchain? -Dmitry -------------- next part -------------- An HTML attachment was scrubbed... URL:

To compile vmkit on Ubuntu 12.04 64-bit machine, I followed the steps giving here <http://vmkit.llvm.org/get_started.html>[1]. but when I run ./configure I am getting following error- root at komal:/home/komal/Desktop/GSOC/vmkit/vmkit# ./configure >> -with-llvm-config-path=../llvm-3.3.src/configure >> --with-gnu-classpath-glibj=/usr/local/classpath/share/classpath/glibj.zip

I downloaded the 3.1 LLVM and Clang sources. I followed the directions at: http://clang.llvm.org/get_started.html I am able to use Clang to compile stuff, but I could already do that with GCC. I'm trying to use Clang for parsing code, but I can't even get started. Can you tell me how to "include the installed location of  clang/llvm headers directories in your include path"?

Those look like the linker is being passed the same .o file built twice, ex: ../Objects-normal/x86_64/asan_globals_test.o ../lib/asan/tests/asan_globals_test.cc.asan.o So, the symbols are colliding. Something is set up wrong in the xcode project. -Nick On Dec 19, 2012, at 9:48 AM, Relph, Richard wrote: > Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM

Hi Kumar, There is an error on your configuration line, you should provide the path to llvm-config binary instead of configure file. Assuming that you compiled llvm in release mode, the llvm-config binary is located in : YOUR_PATH_TO_LLVM/Release+Asserts/bin/llvm-config Try to change the -with-llvm-config-path option and it will compile. Harris Bakiras On 07/19/2013 02:36 PM, Kumar

With VS2013 I found that editing a CMakeLists.txt file caused CMake to be re-run successfully and the build to also continue successfully, but since I switched to VS2015 the CMake re-run occurs - apparently successfully, but more often than not the build failed afterwards from either the IDE and from MSBuild. Since I seldom change the CMakeLists.txt files, I simply do a clean CMake configuration

It looks like building ZERO_CHECK first to reconstruct the project files as needed, then running msbuild a second time to do the actual build, has solved the problem. At least, last night's run didn't take the usual two tries. Running msbuild twice is a little bit simpler than running cmake explicitly, the way I have my scripts set up, but I'm sure that would work as well. Thanks

Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM 3.2 (with clang, extras, and compiler-rt) building - but not testing - on Xcode. I used CMake 2.8.10 GUI to create the Xcode project file. Below are my notes. First, I believe CMake ends up setting things up so that Xcode has 1 warning after scanning the project having to do with hires images or some such… it takes