similar to: [LLVMdev] GCC_NO_EXECUTABLES during CFE build on MinGW

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, 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>

Still trying to build the cfrontend on MinGW: checking for additional debug build... no checking for extra compiler flags for building... checking for sys/types.h... (cached) yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking for main in -lm...

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, 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, 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 Sunday, May 14, 2006, 5:21:49 PM: GP> Do I still need to do the "black magic"? In fact, yes. GP> What is this patched version of bash (do you have a patch, where do I get GP> it?) What does "pwd builtin was just hardly disabled" mean? There are some set of built-in commands in bash (they are called "builtins"). For example

Anton Korobeynikov <asl at math.spbu.ru> writes: [snip] > 2) Problem: Complains about gthr-default.h file. > Resolution: Grab gcc/gcc/gthr-win32.h file and copy it to gthr-default.h ... so --enable-threads=win32 is broken... good to know. > 3) Problem: Complains about "CL_ObjCXX" and simular ("CL_") during > compilation

Hi, John Chriswell wrote: >You might want to google for AC_NO_EXECUTABLES. It's an autoconf test that >generates the >behavior you describe. Apparently the GCC folks wrote a new >version of the macro due to the >above behavior. As suggested, I googled and found this interesting answer for above error and behavior: http://www.mail-archive.com/gcc-bugs at

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 >

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, 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, Reid. You wrote Saturday, February 19, 2005, 6:49:30 AM: RS> i686-pc-cygwin RS> don't know about mingw. i686-pc-mingw32 for mingw. -- With best regards, Anton mailto:asl at math.spbu.ru Saturday, February 19, 2005 9:07:04 AM Faculty of Mathematics & Mechanics, Saint-Petersburg State University

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, 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, Aaron. You wrote Sunday, April 30, 2006, 1:34:16 AM: AG> I traced the code its easy enough to find the error message in the bfd code. Hmm. This seems to be another bug. I've just got access to null address in linker and it's crashed. No error message at all. -- With best regards, Anton mailto:asl at math.spbu.ru Sunday, April 30, 2006 1:48:15 AM

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

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