similar to: [LLVMdev] Cygwin and MingW target triples

Hello, Reid. You wrote Friday, January 21, 2005, 11:14:41 PM: RS> FYI, work progresses on the Win32 native port which you might also find RS> interesting. It might even get done before the cygwin stuff. Jeff Cohen RS> is working on that. Perhaps he can indicate the status of that effort. There is too much work to do native Win32 builds. I've tried to get llvm compiled on mingw32

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

Hello, Reid. You wrote Saturday, June 3, 2006, 10:25:13 PM: RS> I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've RS> tried and failed. There was some message in this list saying, that bootstrap was succeeded on linux. -- With best regards, Anton mailto:asl at math.spbu.ru Saturday, June 3, 2006 10:36:47 PM Faculty of Mathematics

Hello, Reid. You wrote Tuesday, May 16, 2006, 11:13:19 PM: RS> What does the assertion say? The same text, as in the original e-mail: <=cut=> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: BFD 2.16.91 20050610 assertion fail /netrel/src/binutils-20050610-1/bfd/cofflink.c:1926 <=cut=> This assertions is in big function named: bfd_boolean

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

Hello, Jeff. You wrote Saturday, April 29, 2006, 10:45:02 PM: JC> Yes, I know mingw doesn't support dbghelp. I can still rant about it :) ;) Well. Maybe this library will be included in some next versions of mingw's win32api package. Anyway, we can make such library just "on-fly" from the corresponding .dll. JC> This is what's already there. What changed? 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, 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>

BTW: I've also had to make this change when building tools. (I'm building right now and noticed that it doesn't come up anymore, maybe someone checked it in in the last week or so) On Sat, 29 Apr 2006, Anton Korobeynikov wrote: > Hello, Jeff. > > You wrote Saturday, April 29, 2006, 10:45:02 PM: > > JC> Yes, I know mingw doesn't support dbghelp. I can still rant

Hello, Jeff. You wrote Saturday, April 29, 2006, 7:35:46 PM: JC> Bison 1.875 is known to have problems building LLVM. Please upgrade to JC> a newer version (at least 1.875d). The current version is 2.1. Hmm.. I haven't found any problem building LLVM with that bison. ;) The problem, when ld crashed compiling llc is much more serious. It seems to be linker bug. -- With best regards,

Hello, Jeff. You wrote Saturday, April 29, 2006, 10:50:08 PM: JC> You will. You haven't gotten that far yet. It shows up as a crash JC> running gccas. Ok. Switched to 2.1 JC> As for ld crashing, I have no suggestions. It seems to be bug in bfd/cofflink.c file of libbfd. I can even name the function, where weird thing happens. But it's out of my possibilities to debug this

Hello, Jeff. You wrote Saturday, January 22, 2005, 3:57:28 AM: JC> Reid, the binary/text mode is a valid issue. This set of flags worked for me: std::ios_base::out | std::ios_base::trunc | std::ios_base::binary Yes, there are open issues with std::ios_base::binary, but llvm are not affected with them now. JC> I have successfully used a bytecode file on Windows that was created JC> on

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)

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

Hello, llvm-dev. thank you for your interest in my question. Currently, I compiled simple c source code (hello.c) in lunux and windows, and I tried to simple test . first case: hello.bc (compiled with "-emit-llvm" on windows) -> lli.exe(linux). second case: hello.bc (compiled with "-emit-llvm" on linux) -> lli.exe(windows). second case return good result. but First case

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

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

Hello, Aaron. You wrote Sunday, April 30, 2006, 12:01:10 AM: AG> The Cygwin LLVM release (OPTIMIZED_ENABLED) version triggers a bug in LD AG> (BFD binutils) this may well be common to MinGW as well. Seems so, since debug version of llc.exe builds smoothly. Do you have more information about this issue? -- With best regards, Anton mailto:asl at math.spbu.ru

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

Does anyone know what target triples are used for Cygwin and mingw? If someone has a GCC compiler available for one of these systems, typing 'gcc -v' should tell. Thanks! -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/