similar to: [LLVMdev] Compiling Kaleidoscope on Windows

Thanks to OvermindDL1 for pointing this out: compiling with Visual C++ actually works! Basically it's just a matter of running cmake (default settings are fine) then nmake, and I've got what appears to be a working version of LLVM. Kaleidoscope crashes on attempting to exit with ^Z: C:\llvm\bin>Kaleidoscope.exe ready> 1+2; ready> Evaluated to 3.000000 ready> 3*4; ready>

I don't suppose anyone knows what (or how to find out what) the actual command to compile Kaleidoscope is? I followed cmake/nmake down through maybe half a dozen levels before getting lost, so I tried to develop a compiler invocation from scratch. I got as far as cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp which successfully generated toy.obj and spat out 86 link time

Well... that didn't take long. I'm not sure what you did, Reid, with Path.cpp, but it broke VC++: Bytecode.lib(ReaderWrappers.obj) : error LNK2001: unresolved external symbol "public: __thiscall llvm::sys::Path::Path(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0Path at sys@llvm@@QAE at

Hi guys, I discovered xapian today and I'm trying it because it looks promising compared to other FTS engines. However I'm in a windows environment so it's a bit painful to set up as there is no official binaries. I've heard about http://www.flax.co.uk/xapian_binaries And I'm trying to build their latest release (1.2.8). After a few tries I manage to compile everything with

Hi Jeff, Typically, I've found out that these missing functions are placed beneath lib/System/Unix in some of *.cpp files. These function can be copied to their respectively lib/System/Win32 *.cpp files. Henrik. ----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at

Hello all. I decided to see how things were progressing and have updated my Swig to 1.3.29 and my wxWindows to 2.6.3. I''ll try rebuilding everything as soon as I''m done compiling wx 2.6.3. Then I hope to have some time to read up on the new ruby stuff in Swig to see if we can close the last few holes. Roy

On Fri, Dec 5, 2008 at 1:52 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > / * snip */ Actually, rebuilding it makes "debug tblgen" fail with the errors at the end of this email, and as such everything that depends on it, how odd... When I get back to that computer then I will clean its directory, update from SVN (please fix the const thing soon :) ), and rebuild fresh...

On Fri, Dec 5, 2008 at 1:57 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > On Fri, Dec 5, 2008 at 1:52 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: >> / * snip */ > > Actually, rebuilding it makes "debug tblgen" fail with the errors at > the end of this email, and as such everything that depends on it, how > odd... > When I get back to that

Hello, Sorry for bothering You with so many questions, but I''m trying to build wxruby from svn and wxWindgets 2.8.8 using Visual C++ 2008 Express Edition. I builded wxWindgets following instructions http://wiki.wxwidgets.org/Compiling_WxWidgets and http://wxruby.rubyforge.org/wiki/wiki.pl?HowToBuildWxWidgets It compiled without any errors. But on linking step of wxruby build process error

Russell Wallace <russell.wallace at gmail.com> writes: > I don't suppose anyone knows what (or how to find out what) the actual > command to compile Kaleidoscope is? I followed cmake/nmake down > through maybe half a dozen levels before getting lost, so I tried to > develop a compiler invocation from scratch. I got as far as > > cl /EHsc /I\d\llvm-2.6\include

Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in current trunk? [ 95%] Linking CXX executable ../../bin/llvm-objdump Undefined symbols for architecture x86_64: "_xar_serialize", referenced from: DumpBitcodeSection(llvm::object::MachOObjectFile*, char const*, unsigned int, bool, bool, bool, std::__1::basic_string<char, std::__1::char_traits<char>,

On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote: > Kevin Enderby added those symbol uses in r270491. It has a cmake > feature test, and all the uses of those symbols appear bracketed in > HAVE_LIBXAR, so I don't know what went wrong for you. The trigger for this build failure is the usage of -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that

I am writing an interprocedural compiler pass. Because the passneeds information from a FunctionPass, e.g., the post-dominance frontier (PDF), and because a ModulePass is not permitted to require a FunctionPass, I am forced to make my pass a FunctionPass and do majority of its work in the doFinalization() method. When I run "opt -mypass -verify -o code2.bc code1.bc" I get no

I followed what you said and called verifyModule() with the AbortProcessAction option. verifyModule() returns false, but does not abort and does not print out any information about what caused the verification to fail. Chris Lattner wrote: > On Wed, 21 Feb 2007, Ryan M. Lefever wrote: >> I am writing an interprocedural compiler pass. Because the passneeds >> information from a

On Tue, May 24, 2016 at 1:24 PM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > On Tue, May 24, 2016 at 1:22 PM, Jack Howarth > <howarth.mailing.lists at gmail.com> wrote: >> On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote: >>> Kevin Enderby added those symbol uses in r270491. It has a cmake >>> feature test, and

I have a compiler transform that I have been working on that produces bytecode that passes the verifier. However, when I try to read that bytecode back in, I get the assertion failure below. llvm::BytecodeReader::ParseConstantPoolValue(unsigned int): Assertion `(!isa<Constant>(Result) || !cast<Constant>(Result)->isNullValue()) || !hasImplicitNull(TypeID) &&

In my code here https://github.com/DragonOsman/currency_converter , I used C++17 and managed to get it to work (though I'm only using std::map::insert_or_assign() from C++17). And I'm using Windows, so I shouldn't use LDFLAGS or CXXFLAGS as environment variables. I'll use them directly on the compiler command line instead. The libraries I need to link against are

Kevin Enderby added those symbol uses in r270491. It has a cmake feature test, and all the uses of those symbols appear bracketed in HAVE_LIBXAR, so I don't know what went wrong for you. On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in > current trunk? > > [

Are you linking with a C++ compiler? A lot of those missing symbols look like they come from the C++ standard library. -David Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> writes: > @blubee blubeeme So what do you think? Got any ideas? > ---------------------------------------------------------------------- > From: Osman Zakir <osmanzakir90

On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote: > Jack, > > What version of CMake are you using? > > -Chris Chris, I am using cmake 3.5.2. My read of this problem is as follows. While libLLVM.dylib is being linked against -lxar when -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib is created with -Wl,-dead_strip such that