similar to: [LLVMdev] llvm-config on windows

Hello, Duncan > I discovered one other thing that was causing me problems on MinGW: if I use the > msys.bat to open a terminal llvm-config inserts double slashes at the start of > any absolute path it generates (e.g. //lib/LLVMX86CodeGen.o) - this breaks g++. That's strange, never seen this before. Do you have two different version of perl installed? (for example, one msys DTK and

> Make sure you're using the correct perl - that one which comes with msys DTK I'm using msys perl for msys 1.0.11. Maybe I should revert back to msys 1.0.10? ________________________________ Dari: Anton Korobeynikov <anton at korobeynikov.info> Kepada: leledumbo <leledumbo_cool at yahoo.co.id> Cc: llvmdev at cs.uiuc.edu Terkirim: Sen, 27 September, 2010 13:45:47 Judul:

> first line saying: --export-dynamic is not supported for PE targets, do you > mean --export-all-symbols? *or something similar to this* then a bunch of > undefined references occur. Make sure you're using the correct perl - that one which comes with msys DTK -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello, > make[1]: *** [/d/apps/llvm/tools/llvm-config/LibDeps.txt] Error 127 > make[1]: Leaving directory `/d/apps/llvm/tools/llvm-config' > make: *** [all] Error 1 > > It seems as though GenLibDeps.pl does not exist but in fact it does exist in > that directory. I am baffled by that. > I don't really know much about Perl so I can't say if it failed while >

Sam, > Am I supposed to install MinGW (maybe MSYS) and extract prebuilt > packages ( llvm-2.1-x86-mingw32.tar.bz2 and > llvm-gcc4.0-2.1-x86-mingw32.tar.bz2) to C:\MinGW ?? llvm-as != as. You'll need to have binutils installed in order to compile & link. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

Hi Thanks for the info, it led to the source of the error I was having. I was using llvm-gcc binaries (built with mingw I guess) to compile a .c file that is my language runtime, llvm-link'ing that with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

Finally, I got my hands on Windows machine again today. I extracted llvm-2.1-x86-mingw32.tar.bz2 and llvm-gcc4.0-2.1-x86-mingw32.tar.bz2 to C:\llvm (It's a bare Windows Vista installation without MinGW) Added C:\llvm\bin;C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 to PATH (C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 was added for cc1.exe) Downloaded

The alloca hook is in lib\System\Win32\DynamicLibrary.inc all the way at the bottom. You'll see a __MING32__ #ifdef around the definition. You just have to implement those methods and it'll work just fine. Jake On 6/24/07, Scott Graham <scott.llvm at h4ck3r.net> wrote: > > Hi > > Thanks for the info, it led to the source of the error I was having. > > I was using

Hello, Oscar. You wrote Sunday, April 23, 2006, 8:31:14 PM: OF> Forward works ok with MinGW. Back slashes can be interpreted as escape OF> sequences by MSYS/Cygwin tools. I've succeeded in building CFE in Mingw at some 1.3-1.4 release. After, I just don't have enough time to play with LLVM. I've sent my instructions to Henrik Bach <henrik_bach_llvm at hotmail.com>, maybe

Hello, Greg. You wrote Saturday, May 6, 2006, 10:54:19 PM: GP> Is it possible to build using MINGW, but without using msys? GP> All along I've been assuming that I needed msys. Unfortunately, no (especially, if you want to build gcc). LLVM and gcc uses auto* machinery, which depends on sh, sed, sort, etc. So, you should use (at least for configure) some amount of

Hello, Jonathan > I thought I'd messed up something related to the linker, > but I couldn't explain why XP would work using the same steps. The only thing comes to my mind seeing this: perl from msysDTK works differently (somehow) on Vista, thus llvm-config is broken which leads to missed libraries, broken dependencies, etc. I'd suggest you to compare stuff on different

Hello, Everyone. Now I have some spare time and I've decided to build LLVM on Mingw. I've grab the latest 1.7 release (not CVS snapshot). Here are some issues fixed during the build. Now I'm preparing gcc build. So, I think, there will some other "parts" 1. Prerequisites 1.1 GCC 3.4.5 from mingw.org site. $ gcc --version gcc.exe (GCC) 3.4.5 (mingw special) Copyright (C)

Hi Anton, You're already a part of the llvm development team by participating actively on the llvm development list :) If you wish we can put you on: http://llvm.cs.uiuc.edu/Developers.html Great to have you on the team, welcome! We (Jeff, Morten, Paolo, the rest of the team and I) are looking forward to cooperate with you and to push win32 and mingw versions even further to stable and

Anton Korobeynikov wrote: > > > You should have Perl installed. As you're probably using msys, you > should also install msys-dtk, which includes perl for msys. > > -- > With best regards, Anton Korobeynikov. > > > I installed msys-dtk as suggested and got just a bit further. My mingw gcc is version 3.4.2. Thanks for the help so far. I actually had

How can a frontend tell LLVM to put a function argument on stack/register/etc? On Thu, Oct 4, 2012 at 5:08 PM, Anton Korobeynikov <asl at math.spbu.ru> wrote: >> Ah, got it. >> Sounds like we might need to introduce CC_X86_Win32_MSVC_ThisCall then?.. > No, we should not. It should be properly expanded in frontend. > > -- > With best regards, Anton Korobeynikov >

Hello, Bob > download the latest from the head of the trunk, then ran 'configure' under > msys and received the following....  has anyone done this under msys on a > windows pc?? Msys works fine for me. What is the version of msys you're using? What is the version of bash? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

Hello, Greg. You wrote Sunday, May 7, 2006, 10:46:34 PM: GP> 3. One potential point of control is the INCLUDES variable found in GP> cfrontent/gcc/Makefile.in: GP> INCLUDES = -I. -I$(@D) -I$(srcdir) -I$(srcdir)/$(@D) \ GP> -I$(srcdir)/../include @INCINTL@ Just unpack mingw32's headers & libs (w32api && mingw-runtime) into prefix directory. And configure script

Hello, Greg. You wrote Saturday, May 13, 2006, 11:12:26 PM: GP> The problem is that it can't find some symbols: (SymSetOptions, GP> SymInitialize, SymGetModuleBase, SymFunctionTableAccess, etc.) GP> I looked on the Web and these functions are in Dbghelp.lib. GP> Are they also in libimagehlp.a? Yes, they are. At least im mingw-runtime 3.9 (I'm using this version). GP>