Anton Korobeynikov
2005-Jan-21 22:27 UTC
[LLVMdev] making cygwin nightly builds available?
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 using the latest snapshot of gcc from cvs + some mingw specific patches. A (very brief) list of suggested patches: 1. Fix file open mode everywhere! Some llvm tools open files for binary output as text files(!). This leads to corrupted files almost everywhere. (BytecodeWriter, Archive, Linker, ...) 2. Fix CRLF issues, where possible (Archive, etc) 3. Need complete Win32/Path.cpp rewrote to handle all types of paths :( 4. Change __MINGW define to __MINGW32__, which is official now 5. Cfrontend build is little bit tricky, but I have it compiled. The main problems are due to several bugs in mingw's sh.exe implementation, which stops building libstdc++ and many others. Solution: add correct include path to configure script, fix makefile (gcc throws error, if get -I without any path), fix several config bugs (rand48, some in libstdc++). 6. Add stubs for functions in the debugger support library (fork, waitpid, etc.). I have implementation for some of that functions, but not for all. 7. Add -lpsapi -limagehlp to ExtraLibs to all tools' makefiles. .... \infty [Some dummy things, I've forgotten] As result: mingw port seems don't work now, but can in the nearest future. I have patches for some problems I've listed, but I need to sync them with the latest cvs snapshot. I'll send them, when I will be less busy. PS: I've successfully build llvm on cygwin with gcc-3.4.4 without any big problems, maybe only just dummy fixes. -- With best regards, Anton mailto:asl at math.spbu.ru Saturday, January 22, 2005 1:11:19 AM Faculty of Mathematics & Mechanics, Saint-Petersburg State University
I am doing the port using Microsoft's Visual Studio, not mingw. I cannot address mingw-specific problems, but someone here (Henrik) has successfully built with mingw. Reid, the binary/text mode is a valid issue. I have successfully used a bytecode file on Windows that was created on Unix, but I must have been lucky. I don't understand why Win32/Path.cpp needs a complete rewrite to handle all types of paths. What types of paths are not being handled? Trying to get the debugger support library to compile is a waste of time. There is no way it will work on Windows because it actually *uses* fork(). Stubbing it out so it compiles or links will not accomplish anything. A new implementation using the Win32 debugging API is required for it to work. You're welcome to write one :) Anton Korobeynikov wrote:>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 using the latest snapshot >of gcc from cvs + some mingw specific patches. >A (very brief) list of suggested patches: > >1. Fix file open mode everywhere! Some llvm tools open files for binary >output as text files(!). This leads to corrupted files almost everywhere. >(BytecodeWriter, Archive, Linker, ...) >2. Fix CRLF issues, where possible (Archive, etc) >3. Need complete Win32/Path.cpp rewrote to handle all types of paths >:( >4. Change __MINGW define to __MINGW32__, which is official now >5. Cfrontend build is little bit tricky, but I have it compiled. The >main problems are due to several bugs in mingw's sh.exe >implementation, which stops building libstdc++ and many others. >Solution: add correct include path to configure script, fix makefile >(gcc throws error, if get -I without any path), fix several config >bugs (rand48, some in libstdc++). >6. Add stubs for functions in the debugger support library (fork, >waitpid, etc.). I have implementation for some of that functions, but >not for all. >7. Add -lpsapi -limagehlp to ExtraLibs to all tools' makefiles. >.... >\infty [Some dummy things, I've forgotten] > >As result: mingw port seems don't work now, but can in the nearest >future. > >I have patches for some problems I've listed, but I need to sync them >with the latest cvs snapshot. I'll send them, when I will be less >busy. > >PS: I've successfully build llvm on cygwin with gcc-3.4.4 without any big problems, >maybe only just dummy fixes. > > >
Hi Anton, I'm the one who tries to build the mingw version of the llvm stuff in cooperation with the other llvm people. If you would be so kind to ship your list for building the llvm-gcc part we would appriciate it. Or, even better: join the llvm development team. Henrik. ----Original Message Follows---- From: Anton Korobeynikov Date: Sat, 22 Jan 2005 01:27:51 +0300 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 using the latest snapshot of gcc from cvs + some mingw specific patches. A (very brief) list of suggested patches: 1. Fix file open mode everywhere! Some llvm tools open files for binary output as text files(!). This leads to corrupted files almost everywhere. (BytecodeWriter, Archive, Linker, ...) 2. Fix CRLF issues, where possible (Archive, etc) 3. Need complete Win32/Path.cpp rewrote to handle all types of paths :( 4. Change __MINGW define to __MINGW32__, which is official now 5. Cfrontend build is little bit tricky, but I have it compiled. The main problems are due to several bugs in mingw's sh.exe implementation, which stops building libstdc++ and many others. Solution: add correct include path to configure script, fix makefile (gcc throws error, if get -I without any path), fix several config bugs (rand48, some in libstdc++). 6. Add stubs for functions in the debugger support library (fork, waitpid, etc.). I have implementation for some of that functions, but not for all. 7. Add -lpsapi -limagehlp to ExtraLibs to all tools' makefiles. .... \infty [Some dummy things, I've forgotten] As result: mingw port seems don't work now, but can in the nearest future. I have patches for some problems I've listed, but I need to sync them with the latest cvs snapshot. I'll send them, when I will be less busy. PS: I've successfully build llvm on cygwin with gcc-3.4.4 without any big problems, maybe only just dummy fixes. -- With best regards, Anton mailto:asl at math.spbu.ru Saturday, January 22, 2005 1:11:19 AM Faculty of Mathematics & Mechanics, Saint-Petersburg State University _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/