Please show us "./config.status --version", thank you.
eg. $ ./config.status --version
llvm config.status 2.9svn
configured by ../../llvm-cur/configure, generated by GNU Autoconf 2.63,
with options "'-C' '--disable-docs' '--enable-pthreads'
'--enable-optimized' '--enable-assertions=yes'
'--prefix=/c/Users/chapuni/llvm/build/msys-shared/install/stage1'
'--enable-shared=yes' '--enable-targets=all' 'CXX=ccache g++'"
Copyright (C) 2008 Free Software Foundation, Inc.
This config.status script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
-------------------------------------------------------------------------
here is the report:
/e/clang_build/llvm
$ ./config.status --version
llvm config.status 2.9svn
configured by ./configure, generated by GNU Autoconf 2.60,
with options ""
Copyright (C) 2006 Free Software Foundation, Inc.
This config.status script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
-------------------------------------------------------------------------
In-place configure (./configure) might be bad sometimes,
and you may try configure on dedicated build directory, thank you.
$ mkdir /path/to/build
$ cd /path/to/build
$ /path/to/llvm/configure
$ make
I will investigate what would be wrong by in-place configure, someday.
Thanks.
In-fact, I have tried to build in an dedicated directory, ( I have create a separate directory /e/clang_build/build )
and do the configure like:
../llvm/configure
but it gives the same make command error.
In-fact, I have tried to build in an dedicated directory, ( I have create a
separate directory /e/clang_build/build )
and do the configure like:
../llvm/configure
but it gives the same make command error.
I doubt something would be insane to your environment.
- Make sure llvm's source tree is not dirty with garbage of in-place
configure.
- Don't source directory and build directory contain space character
or non-ascii character?
(It would be okay as far as your log)
- Is your msys sane?
With which (or type), check paths for sh, grep, sort, make, sed, and perl.
and confirm versions for toolchain.
Please show us "config.log(.gz)" and "Makefile.config" if you did not
find any problems.
...Takumi
It seems my msys system is ok. ( I have used it to build a windows version of GDB some days ago). When trying to build clang, I have just add the perl-msys package recently.
I just add the attachment (which contains the config.log and Makefile.config files. (these files was generated by in-place configure, strange that I can't do the configure from other directory, the configure command will compliant that "in-place" configure is already used..... then just exit, I'm not sure how to clean the in-place garbage of the in-place configure)
I am sorry, I had to tell you exactly how to seek garbages.
llvm-svn has the attribute svn:ignore.
from command line, svn st --no-ignore
with tsvn, in "Check for modifications...", check "Show unversioned
files" and "Show ignored files".
(you may delete files listed on the dialog)
I have tried configure with TortoiseSVN-1.6.11 and msysgit on Drive D: (/d/).
I don't find any problems with my environment.
If you have another version of GNU Make, try one, too.
...Takumi
Good news!!!
I just delete the make.exe in my mingw/bin folder.
Now, the "which make" command just show another make, which is under bin/ (this is the folder of MSYS/bin)
running make, good, it's compiling now.
You MUST use msys make, mingw make should NOT be in path if you use
msys or it should be named mingw32-make.exe or such so it doesnt get
picked up.
If you fix this you should be able to build it.
Yes, I'm just replying your last post. I'm sorry for my mistake!!!
I will report the build status (if any build issue) later.
Hi, every one.
After building for about One hour, I have successfully build the clang.
Oh my god, the build folder size is 3.5G!
and the folder \build\Debug+Asserts is 2.5G.
especially, under the folder: \build\Debug+Asserts\bin
clang++.exe 430M
clang.exe 430M
llc.exe 170M
....
why these files were so big? (just because Debug enabled?)
After strip command, the clang++.exe is about 20M.
I just test the codecompletion method mentioned in this page (My original test for a cross build clang.exe)
it seems very thing works fine!
Great!thanks all guys for your help.
BTW:
I'm not sure how easy/difficult it is integrate the clang module to an IDE like codeblocks. we need a lot of feature:
1, collecting tags, this is called "batch parsing" in codeblocks : this involve parsing all the files, for clang is should parse all the translation unit. hope PCH can make the parsing much faster. we don't need parse the function body, because we are not interested about local variables.
2, supply some tag-tree structure, so that people can navigate the source from here to there, or jump from declaration to definition.
3, codecompletion, this time, the local variable in the current function scope should be parsed.
additional feature:
code re-factoring (re-name some identifiers)
But you can also use the Official mingw 4.4 or the TDM-MinGW 4.5.1
3, configure(edit) the file
msys\etc\fstab
like: (my mingw was installed under d:/mingw)
d:/mingw /mingw
F:/cb/python27 /python
So that the MSYS system can find your MinGW compiler
4, download the llvm trunk and clang trunk.
and follow the steps like (the folder named "build" was along the llvm folder, the make option will build a release version, if you use the default option, the output file will eat 3G of your hard disk, but in release mode, it only eat 300M+)
cd build
../llvm/configure
make ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1