configure: error: I suspect your system does not have 32-bit development libraries (libc and headers). If you have them, rerun configure with --enable-multilib. If you do not have them, and want to build a 64-bit-only compiler, rerun configure with --disable-multilib.
# yum install glibc-devel*.i686
# cd /etc/yum.repos.d/ # wget -O /etc/yum.repos.d/slc6-devtoolset.repo http://linuxsoft.cern.ch/cern/devtoolset/slc6-devtoolset.repo # yum install devtoolset-2 --nogpgcheck # scl enable devtoolset-2 bash
# cd /etc/yum.repos.d/ # wget -O /etc/yum.repos.d/slc5-devtoolset.repo http://linuxsoft.cern.ch/cern/devtoolset/slc5-devtoolset.repo # yum install devtoolset-1.1 # scl enable devtoolset-1.1 bash
# cd /root/gsl-1.15/ # mkdir build-gsl # cd build-gsl # ../configure --prefix=/usr/local/gsl-1.16/ # make # make install
export PATH=$PATH:/usr/local/gcc-4.8.2/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/gcc-4.8.1/lib
# ./configure --prefix=/usr/local/openmpi-1.6.5-gcc-4.8.1 \ F77=gfortran FC=gfortran --with-devel-headers --enable-binaries
..... g++: unrecognized option '-static-libstdc++' conftest.cpp:11:2: error: #error -static-libstdc++ not implemented .....
# yum install glibc-static glibc-devel glibc-static libstdc++ libstdc++-devel
# bunzip2 gmp-4.3.2.tar.bz2 # tar -zxvf gmp-4.3.2.tar # cd gmp-4.3.2 # ./configure --prefix=/usr/local/gmp-4.3.2 # make # make install
# bunzip2 mpfr-2.4.2.tar.bz2 # tar -zxvf mpfr-2.4.2.tar # cd mpfr-2.4.2 # ./configure --prefix=/usr/local/mpfr-2.4.2 --with-gmp=/usr/local/gmp-4.3.2/ # make # make install
# tar -zxvf mpc-0.8.1.tar.gz # cd mpc-0.8.1 #./configure --prefix=/usr/local/mpc-0.8.1/ --with-gmp=/usr/local/gmp-4.3.2/ --with-mpfr=/usr/local/mpfr-2.4.2 # make # make install
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/mpc-0.8.1:/usr/local/mpfr-2.4.2/lib:/usr/local/gmp-4.3.2/lib
# tar -zxvf gcc-4.7.2.tar.gz # cd gcc-4.7.2 # mkdir build-gcc # cd build-gcc # ../configure --prefix=/usr/local/gcc-4.7.2 \ --with-mpfr=/usr/local/mpfr-2.4.2 \ --with-mpc=/usr/local/mpc-0.8.1 \ --with-gmp=/usr/local/gmp-4.3.2 \ --with-mpfr-include=/usr/local/mpfr-2.4.2/include \ --with-mpc-include=/usr/local/mpc-0.8.1/include # make all-gcc # make install-gcc # make -j 8 # make -j 8 install
# yum install gcc44 gcc44-c++ gcc44-gfortran
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+. Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify their locations. Source code for these libraries can be found at their respective hosting sites as well as at ftp://gcc.gnu.org/pub/gcc/infrastructure/To resolve the issue, download from the ftp://gcc.gnu.org/pub/gcc/infrastructure/ the following application and compile them.
# bunzip2 gmp-4.3.2.tar.bz2 # tar -zxvf gmp-4.3.2.tar # cd gmp-4.3.2 # ./configure --prefix=/usr/local/gmp-4.3.2 # make # make install
# bunzip2 mpfr-2.4.2.tar.bz2 # tar -zxvf mpfr-2.4.2.tar # cd mpfr-2.4.2 # ./configure --prefix=/usr/local/mpfr-2.4.2 --with-gmp=/usr/local/gmp-4.3.2/ # make # make install
# tar -zxvf mpc-0.8.1.tar.gz # cd mpc-0.8.1 #./configure --prefix=/usr/local/mpc-0.8.1/ --with-gmp=/usr/local/gmp-4.3.2/ --with-mpfr=/usr/local/mpfr-2.4.2 # make # make install
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/mpc-0.8.1
# tar -zxvf gcc-4.8.1.tar.gz # cd gcc-4.8.1 # mkdir build-gcc # cd build-gcc # ../configure --prefix=/usr/local/gcc-4.8.1 --with-mpfr=/usr/local/mpfr-2.4.2 --with-mpc=/usr/local/mpc-0.8.1 --with-gmp=/usr/local/gmp-4.3.2 # make # make install
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory compilation terminated. make: *** Error 1
# yum install glibc-devel.i686
ScaLAPACK is a library of high-performance linear algebra routines for distributed-memory message-passing MIMD computers and networks of workstations supporting PVM [68] and/or MPI [64, 110]There are 2 ways you can compile ScaLAPACK, you can download scalapack.tgz and manually compile. Do look at the excellent article ScaLAPACK, LAPACK, BLACS and ATLAS on OpenMPI Linux installation tutorial
# wget http://dl.atrpms.net/el5-x86_64/atrpms/stable/f2c-20031026-3.0.1.el5.x86_64.rpm # rpm -Uvh f2c-20031026-3.0.1.el5.x86_64.rpm # ldconfig
# cd /root # tar -xzvf lapack-3.3.0.tgz # cd /root/lapack-3.3.0 # cp make.inc.example make.incAssuming Edit make.inc. Assuming the Compiling ATLAS on CentOS 5
#BLASLIB = ../../blas$(PLAT).a BLASLIB = /usr/local/atlas/lib/libf77blas.a /usr/local/atlas/lib/libatlas.aCompile lapack package
# makeCopy the libraries to
# mkdir /usr/local/lapack/lib # cp /root/lapack-3.3.0/*.a /usr/local/lapack/lib # cd /usr/local/lapack/lib/ # chmod 555 *.aOther related Information
ATLAS The Automatically Tuned Linear Algebra Software (ATLAS) provides a complete implementation of the BLAS API 3 and a subset of LAPACK 3. A big number of instructions-set specific optimizations are used throughout the library to achieve peak-performance on a wide variety of HW-platforms.MKL
ATLAS provides both C and Fortran interfaces.
ATLAS is available for all HW-platforms capable of running UNIX or UNIX-like operating systems as well as Windows (tm).
Intel's Math Kernel Library (MKL) implements a set of linear algebra, fast Fourier transforms and vector math functions. It includes LAPACK 3, BLAS 3 and extended BLAS and provides both C and Fortran interfaces.Download the latest stable package from ATLAS (http://sourceforge.net/projects/math-atlas/files/Stable/). The current stable version is atlas3.8.0.tar.gz. Do note that ATLAS don't like configuration on its original location, hence the need to create ATLAS_BUILD directory.
MKL is available for Windows (tm) and Linux (x86/i686 and above) only.
# cd /root # tar -xzvf atlas3.8.3.tar.gz # mkdir /root/ATLAS_BUILD # cd /root/ATLAS_BUILD # /root/ATLAS/configureYou will need to turn off CPU Throttling. For CentOS and Fedora, you will use
# /usr/bin/cpufreq-selector -g performanceFor more information, you can see my blog entry Switching off CPU Throttling on CentOS or Fedora
make make check make ptcheck make time make installBy default, ATLAS installed to /usr/local/atlas
At least GCC 3.4 is known to have a broken implementation of the -fvisibility-inlines-hidden flag. The use of this flag is therefore highly discouraged, reported bugs are usually marked as RESOLVED INVALID. See bug 108872 for an example of a typical error message caused by this flag."Case 2: Broken `-fPIC' support checks in configure
Many configure tools check whether the compiler supports the -fPIC flag or not. They do so by compiling a minimalistic program with the -fPIC flag and checking stderr. If the compiler prints *any* warnings, it is assumed that the -fPIC flag is not supported by the compiler and is therefore abandoned. Unfortunately, if the user specifies a non-existing flag (i.e. C++-only flags in CFLAGS or flags introduced by newer versions of GCC but unknown to older ones), GCC prints a warning too, resulting in borkage.
To prevent this kind of breakage, the AMD64 profiles use a bashrc that filters out invalid flags in C[XX]FLAGS.
This is the most common case. It is a real bug in the build system and should be fixed in the ebuild, preferably with a patch that is sent upstream. Assuming the error message looks like this:
This means that the file assert.o was not compiled with the -fPIC flag, which it should. When you fix this kind of error, make sure only objects that are used in shared libraries are compiled with -fPIC.
In this case, globally adding -fPIC to C[XX]FLAGS resolves the issue, although this practice is discouraged because the executables end up being PIC-enabled, too.
Sometimes a package tries to build shared libraries using statically built archives which are not PIC-enabled. There are two main reasons why this happens:
Often it is the result of mixing USE=static and USE=-static. If a library package can be built statically by setting USE=static, it usually doesn't create a .so file but only a .a archive. However, when GCC is given the -l flag to link to said (dynamic or static) library, it falls back to the static archive when it can't find a shared lib. In this case, the preferred solution is to build the static library using the -fPIC flag too.
Sometimes it is also the case that a library isn't intended to be a shared library at all, e.g. because it makes heavy usage of global variables. In this case the solution is to turn the to-be-built shared library into a static one.
# yum install gcc, gcc-c++, gcc-g77, gcc-java
# yum install gcc4, gcc4-c++, gcc4-gfortran, gcc4-javaOr
#yum install gcc4*
