Just wondering, I'm a little outdated about dc devving, what are the best versions for GNU applications for KallistiOS 2.0.0 ?
For example :
- gcc: 4.6.2 (?)
- gdb: ?
- insight: ?
- ...: ?
Thank you in advance!
The latest versions should work fine. Also, as SWAT pointed out, the version of dc-chain in the Git repository automatically downloads and builds all of these for you.SiZiOUS wrote:@BlueCrab, just to know, for building GCC with target SH, I need to download 3 additional libraries:Can I use the lastest versions of libraries safely or not ?
- GNU Multiple Precision Library (GMP) version 4.3.2 (or later) - Lastest is 5.1.3
- MPFR Library version 2.4.2 (or later) - Lastest is 3.1.2
- MPC Library version 0.8.1 (or later) - Lastest is 1.0.1
If not, can I have the best versions number ?
See Installing GCC: Prequisites for the software required to build GCC. If you do not have the GMP, MPFR and MPC support libraries already installed as part of your operating system then there are two simple ways to proceed, and one difficult, error-prone way. For some reason most people choose the difficult way. The easy ways are:
If it provides sufficiently recent versions, use your OS package management system to install the support libraries in standard system locations. For Debian-based systems, including Ubuntu, you should install the packages libgmp-dev, libmpfr-dev and libmpc-dev. For RPM-based systems, including Fedora and SUSE, you should install gmp-devel, mpfr-devel and libmpc-devel (or mpc-devel on SUSE) packages. The packages will install the libraries and headers in standard system directories so they can be found automatically when building GCC.
Alternatively, after extracting the GCC source archive, simply run the ./contrib/download_prerequisites script in the GCC source directory. That will download the support libraries and create symlinks, causing them to be built automatically as part of the GCC build process. Set GRAPHITE_LOOP_OPT=yes in the script if you want to build GCC with the Graphite loop optimizations.
The difficult way, which is not recommended, is to download the sources for GMP, MPFR and MPC, then configure and install each of them in non-standard locations, then configure GCC with --with-gmp=/some/silly/path/gmp --with-mpfr=/some/silly/path/mpfr --with-mpc=/some/silly/path/mpc, then be forced to set LD_LIBRARY_PATH=/some/silly/path/gmp:/some/silly/path/mpfr:/some/silly/path/mpc/lib in your environment forever. This is silly and causes major problems for anyone who doesn't understand how dynamic linkers find libraries at runtime. Do not do this. If building GCC fails when using any of the --with-gmp or --with-mpfr or --with-mpc options then you probably shouldn't be using them.