similar to: [LLVMdev] [RC3] Status on Mingw MSYS

On cygwin-1.7, clang and llvm can be built fine through 3 stages. With --disable-assertions (RC3's default), I saw a few warnings in llvm/lib/AsmParser/LLParser.cpp with g++-4.3.4. (and two warnings, PR9515) ...Takumi $ uname.exe -a CYGWIN_NT-6.1-WOW64 HEAVEN64 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin $ gcc --version gcc (GCC) 4.3.4 20090804 (release) 1 * Stage 1 configured by

Hello guys, On cygwin-1.7, I can build and test clang successfully by 3-stage. Known issues: - binaries among stage2 and stage3 do not match. (other than timestamp and checksum) investigating. - I met some warnings. I have fixes for them. - [llvm] r127241 - [llvm] http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110307/117725.html - [clang] r127283 - [clang]

On 2017-11-13 13:31, Rowland Penny wrote: > On Mon, 13 Nov 2017 13:18:20 +0100 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> Could we please not waste a week poking at random unrelated stuff this >> time? These "I try the same stuff no matter what the problem is" >> boilerplate emails become really grating after the first few times. :/

as part of building python2.5.2 under msys under wine on linux using mingw, i thought i'd try building _msi.pyd just for kicks. of course, that required having an msi.lib import library, and associated header files. so, purely as an experiment, i've documented the process by which it is possible to take wine 1.1.13 (current development release) source code, modify the header files for

folks, hi, this is a fairly important issue for python development interoperability - martin mentioned that releases of mingw-compiled python, if done with a non-interoperable version of msvcrt, would cause much mayhem. well, compiling python on mingw with msvcr80 _can_ be done; using it can also be a simple matter of creating a python.exe.manifest file, but i can't actually do any testing

hi folks, i promised i'd get python built under wine - and i'm happy to report that this goal has been successfully achieved. http://bugs.python.org/issue4954 if anyone's interested. what has been achieved is that a python.exe, libpython2.5.dll, an implib libpython2.5.dll.a and a python2.5.def have all been successfully created using an entirely free software toolchain, along with the

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > [snip] > >> My internal priority for that CMake patch is low, as I need only minimal >> patching to use the autoconf-generated configure script to build LLVM. >> Right now it's just llvm.config.in.in that needs patching (the failsafed >> GenLibDeps.pl script went in

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > >> * I am seeing desynchronization between the configure-generated >> Makefiles and the CMakeFile.txt files. [e.g., llc; makefile doesn't >> have asmprinter, CMakeFile.txt does]. That much I should be able to >> construct a patch for "blind", if no-one gets to it first.

Óscar Fuentes wrote: > The CMake devteam is very responsive about bug reports. They will > certainly appreciate your bug report, no patch required. > I still don't think I have enough detail to file a bug report (not sure exactly what they need to know about my system configuration to make it testable). I did go ahead (just now) and ask the main CMake mailing list which files I

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, Bob > i running msys 1.0 it appears; the bash sh is 2.04.0(1) Hrm... This seems to be pretty ancient and buggy. :) Consider reading http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx it can provide necessary sources of different tools requires. Some versions noted there might be already out-of-date, but otherwise the text looks good. -- With best

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Verdana">hi anton,<br> <br> i upgrade my

-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm.patch Type: application/octet-stream Size: 14374 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090805/4328d661/attachment.obj>

I had Strawberry Perl, which was the problem. I installed the Perl from the MSYS distribution and it now works. I've enclosed a patch for the Getting Started page. Thanks for pointing me in the right direction. -John >On Wed, Aug 5, 2009 at 5:36 PM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > John Thompson wrote: > > Hi, > > > > I'm trying to build

Thank you > 2. As for error - try to disable threads during llvm/llvm-gcc builds. This resolved the build errors for llvm-gcc, however the llvm-gcc.exe, llvm-g++.exe, llvm-gcov.exe were not built only the llc.exe, llvm-as.exe ... tools from the llvm build bin directory are in the llvm-gcc install bin directory. > 1. Why do you need build llvm-gcc by yourself? I would like to write an

Thank you > 2. As for error - try to disable threads during llvm/llvm-gcc builds. This resolved the build errors for llvm-gcc, however the llvm-gcc.exe, llvm-g++.exe, llvm-gcov.exe were not built only the llc.exe, llvm-as.exe ... tools from the llvm build bin directory are in the llvm-gcc install bin directory. > 1. Why do you need build llvm-gcc by yourself? I would like to write an

Hello, Charles >> 2. As for error - try to disable threads during llvm/llvm-gcc builds. > > This resolved the build errors for llvm-gcc, however the llvm-gcc.exe, > llvm-g++.exe, llvm-gcov.exe were not built only the llc.exe, llvm-as.exe ... > tools  from the llvm build bin directory are in the llvm-gcc install bin > directory. Then something is completely broken on your side

I managed to build clang on mingw/msys today. Running configure, make install worked for both debug and optimized builds in general. However there were a few hitches along the way. Make would fail with: ln: creating symbolic link `/d/super/dump/code/llvm/llvm-project/llvm/build.clang/Release+Asserts/bin/clang++.exe' to `clang.exe': No such file or directory ln: creating symbolic link

Good evening, guys! I suppose mingw build would be stable, though, I would like some patches to be picked up. * RC1 LLVM and clang can be built on either msys/autoconf, msys/cmake and mingw/cmake. By CMake, all tests can run but 37 of LLVM and 5 of clang tests would fail. On mingw by configure tests cannot be executed. [PR9505] For compiling, I saw a warning, in llvm-bcanalyzer.cpp. (fixed in

What version? Did you try both 1.2rc1 and git? Jean-Marc Quoting James McIlroy <james.mcilroy at nativ.tv>: > Hiya, > > I'm trying to get speex compiling under windows using MinGW and Msys. > > Sequence of events: > - unpack the speex distribution, then run: > - ./configure --disable-shared > > then it happily goes off and spews out a load of output,