Matthew Bromberg
2005-Oct-30 03:50 UTC
[LLVMdev] Still can't compile backend or frontend on Windows
It's a shame this fine tool can't get better installation support for Windows. If it did I suspect it would get a lot more coverage. After 5 months or so I still have no way to compile the backend tools let alone the C frontend on windows. I have tried both Cygwin and Mingw so far. MingW is preferrable since distributions of the binaries would not require the cygwin.dll. It would be nice if the full backend binaries under windows were available for download. I understand that the VC++ build has downloadable binaries somewhere, but it lacks the final support for generating executable output (correct me if I'm wrong). This time I attempted to compile the CVS version, 1.6 in the hope that it had better support for Windows as some of the release notes seemed to indicate. I followed the Mingw installation instructions on http://www.geocities.com/henrik_bach_llvm/ There were a bunch of Warnings during the configure phase involving missing utilities such as mmap and ldopen(). When I started make I died with the following message: llvm[1]: Compiling IsNAN.cpp for Debug build llvm[1]: Compiling PluginLoader.cpp for Debug build llvm[1]: Compiling SlowOperationInformer.cpp for Debug build In file included from D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperation Informer.cpp:19: D:/Apps/msys/mingw/bin/../lib/gcc/mingw32/3.4.4/../../../../include/unistd.h:13: 27: unistd.h: No such file or directory D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp: In const ructor `llvm::SlowOperationInformer::SlowOperationInformer(const std::string&)': D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp:55: error : `SIGALRM' undeclared (first use this function) D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp:55: error : (Each undeclared identifier is reported only once for each function it appears in.) D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp:57: error : `alarm' undeclared (first use this function) D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp: In destr uctor `llvm::SlowOperationInformer::~SlowOperationInformer()': D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp:69: error : `alarm' undeclared (first use this function) D:/Apps/msys/src/llvmobj/../llvm/lib/Support/SlowOperationInformer.cpp:70: error : `SIGALRM' undeclared (first use this function) make[1]: *** [/src/llvmobj/lib/Support/Debug/SlowOperationInformer.o] Error 1 make[1]: Leaving directory `/src/llvmobj/lib/Support' make: *** [all] Error 1 (sigh) I thought operating system specific headers such as unistd.h were not supposed to be needed. Perhaps someone who has successfully compiled the backend under Windows using Mingw could point me to the binary executables and/or even better some link libraries.
Chris Lattner
2005-Oct-30 05:46 UTC
[LLVMdev] Still can't compile backend or frontend on Windows
On Sat, 29 Oct 2005, Matthew Bromberg wrote:> It's a shame this fine tool can't get better installation support for > Windows. If it did I suspect it would get a lot more coverage. After 5Yup.> months or so I still have no way to compile the backend tools let alone the C > frontend on windows. I have tried both Cygwin and Mingw so far. MingW is > preferrable since distributions of the binaries would not require the > cygwin.dll. It would be nice if the full backend binaries under windows were > available for download. I understand that the VC++ build has downloadable > binaries somewhere, but it lacks the final support for generating executable > output (correct me if I'm wrong).I'm not familiar with the state of the windows build.> This time I attempted to compile the CVS version, 1.6 in the hope that it had > better support for Windows as some of the release notes seemed to indicate. > I followed the Mingw installation instructions on > http://www.geocities.com/henrik_bach_llvm/1.6 has better support for building native with VC++. I know that cygwin works to some degree (though the release build is broken due to cygwin bugs?), but I'm not familiar with the state of mingw. It seems not as good as it could be.> There were a bunch of Warnings during the configure phase involving missing > utilities such as mmap and ldopen(). When I started make I died with the > following message: > llvm[1]: Compiling IsNAN.cpp for Debug build...> (sigh) I thought operating system specific headers such as unistd.h were not > supposed to be needed. Perhaps someone who has successfully compiled the > backend under Windows using Mingw could point me to the binary executables > and/or even better some link libraries.I don't know what the deal is, because I don't use that platform. However, things will not improve unless someone steps forward to contribute patches. If MingW is really important to you, you could dive in and see if you can fix some of the problems. -Chris -- http://nondot.org/sabre/ http://llvm.org/
Aaron Gray
2005-Oct-30 14:38 UTC
[LLVMdev] Still can't compile backend or frontend on Windows
> It's a shame this fine tool can't get better installation support for > Windows. If it did I suspect it would get a lot more coverage. After > 5 months or so I still have no way to compile the backend tools let > alone the C frontend on windows. I have tried both Cygwin and Mingw so > far. MingW is preferrable since distributions of the binaries would not > require the cygwin.dll. It would be nice if the full backend binaries > under windows were available for download. I understand that the VC++ > build has downloadable binaries somewhere, but it lacks the final > support for generating executable output (correct me if I'm wrong).I have build instructions for the debug build on Cygwin :- http://angray.members.beeb.net/llvm/MakingLLVM.html Aaron
Henrik Bach
2005-Oct-30 19:49 UTC
[LLVMdev] Still can't compile backend or frontend on Windows
>From: Chris Lattner >Date: Sun, 30 Oct 2005 00:46:23 -0500 (CDT) > >On Sat, 29 Oct 2005, Matthew Bromberg wrote: >>It's a shame this fine tool can't get better installation support for >>Windows. If it did I suspect it would get a lot more coverage. After 5 > >Yup. > >>months or so I still have no way to compile the backend tools let alone >>the C frontend on windows. I have tried both Cygwin and Mingw so far. >>MingW is preferrable since distributions of the binaries would not require >>the cygwin.dll. It would be nice if the full backend binaries under >>windows were available for download. I understand that the VC++ build has >>downloadable binaries somewhere, but it lacks the final support for >>generating executable output (correct me if I'm wrong). > >I'm not familiar with the state of the windows build. > >>This time I attempted to compile the CVS version, 1.6 in the hope that it >>had better support for Windows as some of the release notes seemed to >>indicate. I followed the Mingw installation instructions on >>http://www.geocities.com/henrik_bach_llvm/ > >1.6 has better support for building native with VC++. I know that cygwin >works to some degree (though the release build is broken due to cygwin >bugs?), but I'm not familiar with the state of mingw. It seems not as good >as it could be. > >>There were a bunch of Warnings during the configure phase involving >>missing utilities such as mmap and ldopen(). When I started make I died >>with the following message: >>llvm[1]: Compiling IsNAN.cpp for Debug build > >... > >>(sigh) I thought operating system specific headers such as unistd.h were >>not supposed to be needed. Perhaps someone who has successfully compiled >>the backend under Windows using Mingw could point me to the binary >>executables and/or even better some link libraries. >Most of these warnings and compile errors are related to the platform specific layer for Unix/Windows. Unfortunately, I haven't got the guts nor time (and currently no windows/mingw platform) to go deeper into how to implement this functionality on the Windows platform. However, I have kept my notes how to get rid of these warnings and compile errors (possibly introducing erractic behavior) for the llvm tools. I'll happily provide these notes and my assistance for whom has the time to provide the community with binaries for Windows. Henrik.> >I don't know what the deal is, because I don't use that platform. However, >things will not improve unless someone steps forward to contribute patches. > If MingW is really important to you, you could dive in and see if you can >fix some of the problems. > >-Chris > >-- >http://nondot.org/sabre/ >http://llvm.org/ > >_______________________________________________ >LLVM Developers mailing list >LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev_________________________________________________________________ Find det, du s�ger p� MSN S�g http://search.msn.dk
Reasonably Related Threads
- [LLVMdev] Re: Still can't compile backend or frontend on, Windows
- [LLVMdev] Re: LLVMdev Digest, Vol 16, Issue 24
- [LLVMdev] Still can't compile backend or frontend on Windows
- [LLVMdev] SlowOperationInformer.cpp:55: error: `SIGALRM' undeclared (first use this functi
- [LLVMdev] SlowOperationInformer.cpp:55: error: `SIGALRM' undeclared (first use this functi