From cTuning.org
Navigation: cTuning.org > CTools > ICI
Contents |
Updating the GIT repository from SVN
Clean up your build space
If you are short on build space, remove the current build using the matching makefiles by doing "make distclean" in the build directory of the compiler (you may want to archive the build - and the sources - as tarballs first). If you (or your quality officer) are paranoid about clean builds, remove the build directory altogether (except maybe for any build traces you may want to keep).
Set up GIT repository contents as starting point
- if you have no GIT workspace:
$ git clone git://gitorious.org/gcc-ici/mainline.git
- if you have a working GIT workspace which you want to update first, first decide whether you want to work on a separate branch; if so, create or select the appropriate branch with git-branch, check the branch out with git-checkout, then update its contents (only if needed) with git-pull:
$ git-branch your-branch-name $ git checkout $ git pull git://gitorious.org/gcc-ici/mainline.git
Sanitize Subversion state
When running Subversion on the source tree checked out from GIT, you may encounter the problem of missing tmp subdirectories in the Subversion internal directiories. During "svn update", the Subversion binary may complain about these directories missing from the workspace and recommend to run "svn cleanup". However, this command is likely to fail too - apparently, running "svn cleanup" is not sufficient, so you need to manually recreate these missing directories. This is quickly done using the following Bourne shell command, to be run from the toplevel of the SVN checkout (currently, "mainline/trunk")
$ for i in `find . -type d -name .svn` ; do [ ! -d $i/tmp ] && mkdir $i/tmp ; done
Update the workspace from the GCC Subversion server
Running "svn update" may trigger conflicts when merging local and remote changes. Whether you want to resolve the conflicts on the fly or after completing the update depends on your personal preferences and practices - YMMV!
Rebuild the compiler from scratch and test
If you have enough disk space (1.5GB per bootstrap build with C only), create a new directory to build the compiler. Otherwise, make sure the build directory is cleaned up ("make distclean" or "rm -rf *").
As a sanity check, make a bootstrap build with only C language enabled (approx. 50 minutes wallclock time on an Athlon64 X2 2.2GHz with 2GB of RAM):
$ ../<path-to-GCC-source>/configure --prefix=<your-destination-prefix> --enable-languages=c