Hi all,
yes, I do not know python and I installed it only for being able to
build LLVM.
Now I have installed version 2.7.
I tried with codeblock project generation, but I'm still getting errors.
So I moved to visual studio as per "getting started" guide.
I run the command: cmake -G "Visual Studio 11" ..\llvm from my build
folder.
It lists a lot of file not found during the execution, but at the end it
does create th visual studio projects.
Based on the web guide, it should be successful.
First question, is it really?
Then, I open visual studio and run the solution compilation.
But, after a long time, I got a lot of errors stating that it is not
possible to find the stdbool.h file + a few others.
Example:
error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such
file or directory (<my
path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my
path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64
error C2061: errore di sintassi: identificatore '__attribute__' (<my
path>\llvm\projects\compiler-rt\lib\int_util.c) <my
path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 clang_rt.x86_64
error C2059: errore di sintassi: ';' (<my
path>\llvm\projects\compiler-rt\lib\int_util.c) <my
path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 clang_rt.x86_64
error C2182: 'noreturn': utilizzo non valido del tipo 'void'
(<my
path>\llvm\projects\compiler-rt\lib\int_util.c) <my
path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 clang_rt.x86_64
error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such
file or directory (<my
path>\llvm\projects\compiler-rt\lib\int_util.c) <my
path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64
What could it be?
Any help is appreciated,
Giorgio
Il 22/07/2013 03.38, Óscar Fuentes ha scritto:> Reid Kleckner <rnk at google.com> writes:
>
>> My initial impression was that still probably nobody uses python 3, so
it's
>> not worth adding support that will break. But if users actually have
>> python 3, maybe it's worth it.
> I think that on this case the problem was not people who actually have
> python 3, but people who see Python as a requirement for building LLVM
> and go to python.org and download the "most recent" version, i.e.
python
> 3, because they are unaware of the incompatibilities. Believe it or not,
> there are developers who don't know about the Python mess :-)
>
> If adding support for version 3 is problematic, a check that gives a
> helpful message would be a good start. If it can't be implemented on
the
> python scripts, it could be implemented on the cmake/configure scripts.
>
> BTW, http://llvm.org/docs/GettingStarted.html mentions Python as a
> requirement for the automated test suite (not for the build.) Says
> version >=2.4. A user reading that would assume that version 3.X is ok,
> or no Python at all if he only wishes to play with LLVM.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
I also tried to build LLVM with 3.3 sources. Same problems. Even worse, Visual Studio hangs and I had to kill the process. What could it be? Is Visual Studio 2012 working with LLVM/clang? Or LLVM/Clang is not supposed to work on windows (I saw also that there are no binaries ready for the windows platform). Thanks in advance, Giorgio Il 22/07/2013 22.51, Giorgio Franceschetti ha scritto:> Hi all, > yes, I do not know python and I installed it only for being able to > build LLVM. > Now I have installed version 2.7. > > I tried with codeblock project generation, but I'm still getting errors. > > So I moved to visual studio as per "getting started" guide. > > I run the command: cmake -G "Visual Studio 11" ..\llvm from my build > folder. > > It lists a lot of file not found during the execution, but at the end > it does create th visual studio projects. > Based on the web guide, it should be successful. > First question, is it really? > > Then, I open visual studio and run the solution compilation. > > But, after a long time, I got a lot of errors stating that it is not > possible to find the stdbool.h file + a few others. > Example: > error C1083: Impossibile aprire il file inclusione 'stdbool.h': No > such file or directory (<my > path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my > path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 > error C2061: errore di sintassi: identificatore '__attribute__' (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 clang_rt.x86_64 > error C2059: errore di sintassi: ';' (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 clang_rt.x86_64 > error C2182: 'noreturn': utilizzo non valido del tipo 'void' (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 clang_rt.x86_64 > error C1083: Impossibile aprire il file inclusione 'stdbool.h': No > such file or directory (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 > > > What could it be? > > Any help is appreciated, > > Giorgio > > Il 22/07/2013 03.38, Óscar Fuentes ha scritto: >> Reid Kleckner <rnk at google.com> writes: >> >>> My initial impression was that still probably nobody uses python 3, >>> so it's >>> not worth adding support that will break. But if users actually have >>> python 3, maybe it's worth it. >> I think that on this case the problem was not people who actually have >> python 3, but people who see Python as a requirement for building LLVM >> and go to python.org and download the "most recent" version, i.e. python >> 3, because they are unaware of the incompatibilities. Believe it or not, >> there are developers who don't know about the Python mess :-) >> >> If adding support for version 3 is problematic, a check that gives a >> helpful message would be a good start. If it can't be implemented on the >> python scripts, it could be implemented on the cmake/configure scripts. >> >> BTW, http://llvm.org/docs/GettingStarted.html mentions Python as a >> requirement for the automated test suite (not for the build.) Says >> version >=2.4. A user reading that would assume that version 3.X is ok, >> or no Python at all if he only wishes to play with LLVM. >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >
Hi Giorgio, here is another description how to compile LLVM on Windows: http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC Maybe this is helpful. I created this for Windows 7 but I also repeated it successfully on Windows 8. Regards Kai On 22.07.2013 22:51, Giorgio Franceschetti wrote:> Hi all, > yes, I do not know python and I installed it only for being able to > build LLVM. > Now I have installed version 2.7. > > I tried with codeblock project generation, but I'm still getting errors. > > So I moved to visual studio as per "getting started" guide. > > I run the command: cmake -G "Visual Studio 11" ..\llvm from my build > folder. > > It lists a lot of file not found during the execution, but at the end it > does create th visual studio projects. > Based on the web guide, it should be successful. > First question, is it really? > > Then, I open visual studio and run the solution compilation. > > But, after a long time, I got a lot of errors stating that it is not > possible to find the stdbool.h file + a few others. > Example: > error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such > file or directory (<my > path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my > path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 > error C2061: errore di sintassi: identificatore '__attribute__' (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 > clang_rt.x86_64 > error C2059: errore di sintassi: ';' (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 > clang_rt.x86_64 > error C2182: 'noreturn': utilizzo non valido del tipo 'void' (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 > clang_rt.x86_64 > error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such > file or directory (<my > path>\llvm\projects\compiler-rt\lib\int_util.c) <my > path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 > > > What could it be? > > Any help is appreciated, > > Giorgio > > Il 22/07/2013 03.38, Óscar Fuentes ha scritto: >> Reid Kleckner <rnk at google.com> writes: >> >>> My initial impression was that still probably nobody uses python 3, >>> so it's >>> not worth adding support that will break. But if users actually have >>> python 3, maybe it's worth it. >> I think that on this case the problem was not people who actually have >> python 3, but people who see Python as a requirement for building LLVM >> and go to python.org and download the "most recent" version, i.e. python >> 3, because they are unaware of the incompatibilities. Believe it or not, >> there are developers who don't know about the Python mess :-) >> >> If adding support for version 3 is problematic, a check that gives a >> helpful message would be a good start. If it can't be implemented on the >> python scripts, it could be implemented on the cmake/configure scripts. >> >> BTW, http://llvm.org/docs/GettingStarted.html mentions Python as a >> requirement for the automated test suite (not for the build.) Says >> version >=2.4. A user reading that would assume that version 3.X is ok, >> or no Python at all if he only wishes to play with LLVM. >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
On my PC it does not work. I'm able to generate and open the Visual studio project (VS 11 Win64). I have tried with cmake on command line, with the cmake gui, release 3.4 and 3.3. But when I try to compile the solution I get a loot of errors about a missing stdbool.h file. Does anyone have any hint? Giorgio Il 23/07/2013 07.44, Kai Nacke ha scritto:> Hi Giorgio, > > here is another description how to compile LLVM on Windows: > http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC > > Maybe this is helpful. I created this for Windows 7 but I also > repeated it successfully on Windows 8. > > Regards > Kai > > On 22.07.2013 22:51, Giorgio Franceschetti wrote: >> Hi all, >> yes, I do not know python and I installed it only for being able to >> build LLVM. >> Now I have installed version 2.7. >> >> I tried with codeblock project generation, but I'm still getting errors. >> >> So I moved to visual studio as per "getting started" guide. >> >> I run the command: cmake -G "Visual Studio 11" ..\llvm from my build >> folder. >> >> It lists a lot of file not found during the execution, but at the end it >> does create th visual studio projects. >> Based on the web guide, it should be successful. >> First question, is it really? >> >> Then, I open visual studio and run the solution compilation. >> >> But, after a long time, I got a lot of errors stating that it is not >> possible to find the stdbool.h file + a few others. >> Example: >> error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such >> file or directory (<my >> path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my >> path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 >> error C2061: errore di sintassi: identificatore '__attribute__' (<my >> path>\llvm\projects\compiler-rt\lib\int_util.c) <my >> path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 >> clang_rt.x86_64 >> error C2059: errore di sintassi: ';' (<my >> path>\llvm\projects\compiler-rt\lib\int_util.c) <my >> path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 >> clang_rt.x86_64 >> error C2182: 'noreturn': utilizzo non valido del tipo 'void' (<my >> path>\llvm\projects\compiler-rt\lib\int_util.c) <my >> path>\llvm\projects\compiler-rt\lib\int_util.h 27 1 >> clang_rt.x86_64 >> error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such >> file or directory (<my >> path>\llvm\projects\compiler-rt\lib\int_util.c) <my >> path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 >> >> >> What could it be? >> >> Any help is appreciated, >> >> Giorgio >> >> Il 22/07/2013 03.38, Óscar Fuentes ha scritto: >>> Reid Kleckner <rnk at google.com> writes: >>> >>>> My initial impression was that still probably nobody uses python 3, >>>> so it's >>>> not worth adding support that will break. But if users actually have >>>> python 3, maybe it's worth it. >>> I think that on this case the problem was not people who actually have >>> python 3, but people who see Python as a requirement for building LLVM >>> and go to python.org and download the "most recent" version, i.e. >>> python >>> 3, because they are unaware of the incompatibilities. Believe it or >>> not, >>> there are developers who don't know about the Python mess :-) >>> >>> If adding support for version 3 is problematic, a check that gives a >>> helpful message would be a good start. If it can't be implemented on >>> the >>> python scripts, it could be implemented on the cmake/configure scripts. >>> >>> BTW, http://llvm.org/docs/GettingStarted.html mentions Python as a >>> requirement for the automated test suite (not for the build.) Says >>> version >=2.4. A user reading that would assume that version 3.X is ok, >>> or no Python at all if he only wishes to play with LLVM. >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> >>> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >
Giorgio Franceschetti <g.franceschetti at vidya.it> writes:> I also tried to build LLVM with 3.3 sources. > Same problems.If you omit compiler-rt, does it work? (compiler-rt is not a required component.)> Even worse, Visual Studio hangs and I had to kill the process. > > What could it be? Is Visual Studio 2012 working with LLVM/clang? > > Or LLVM/Clang is not supposed to work on windows (I saw also that > there are no binaries ready for the windows platform).For the most part, LLVM works fine on Windows, with some limitations. Clang has serious shortcomings, more so if you build it with VS (Mingw is better because Clang can use the headers and standard C++ library that comes with MinGW, but not the standard C++ library that comes with VS.)>> It lists a lot of file not found during the execution, but at the >> end it does create th visual studio projects. >> Based on the web guide, it should be successful. >> First question, is it really?Yes. What you are seeing are the platform checks, where the build system looks for the presence of functions, headers, etc and then generates a configuration file with that information.