On Sun, Jul 21, 2013 at 5:51 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:> Giorgio Franceschetti <g.franceschetti at vidya.it> writes: > > > When I run cmake I got The following error: > > *<project folder>\build>CMake -G "CodeBlocks - MinGW Makefiles" ..\llvm* > > /-- Could NOT find LibXml2 (missing: LIBXML2_LIBRARIES > > LIBXML2_INCLUDE_DIR)// > > //-- Target triple: x86_64-w64-mingw32// > > //-- Native target architecture is X86// > > //-- Threads enabled.// > > //-- Found PythonInterp: C:/Python33/python.exe (found version "3.3.2")// > > //-- Constructing LLVMBuild project information// > > //CMake Error at CMakeLists.txt:299 (message):// > > // Unexpected failure executing llvm-build: Traceback (most recent > > call last):// > > I think that you installed the wrong version of Python. IIRC llvm-build > requires Python 2.X >There was a patch on the commit list to try to make some of our scripts work for both 2 and 3. I should dig it up and review it. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130721/980668b5/attachment.html>
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.
On Jul 22, 2013, at 02:11, Reid Kleckner <rnk at google.com> wrote:> On Sun, Jul 21, 2013 at 5:51 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Giorgio Franceschetti <g.franceschetti at vidya.it> writes:...> I think that you installed the wrong version of Python. IIRC llvm-build > requires Python 2.X > > There was a patch on the commit list to try to make some of our scripts work for both 2 and 3. I should dig it up and review it.See http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130715/181547.html> 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 guess it is slow in coming, but when it gains a certain critical mass, the 2.x series will be doomed quickly. In any case, the patch looks fairly minimal, except for globally replacing "print foo" with "print(foo)", which I wish the Python guys hadn't done. :-) -Dimitry
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
>
>