wiki.chpc.ac.za

User Tools

Site Tools

You are here: start » howto » compiling_gcc
Trace: • compiling_gcc • compilers
howto:compiling_gcc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
howto:compiling_gcc [2012/09/17 10:14]
adymond 		howto:compiling_gcc [2021/12/09 16:42] (current)
Line 4: Line 4:
 GCC version required for their codes. For the official guide on compiling GCC GCC version required for their codes. For the official guide on compiling GCC
 please visit the [[http://gcc.gnu.org/install/|GCC website]]. This guide please visit the [[http://gcc.gnu.org/install/|GCC website]]. This guide
-documents how GCC would be built on the Sun Tsessbe Cluster login node,+documents how GCC 4.7.1 would be built on the Sun Tsessbe Cluster login node,
 after the August 2012 upgrades. after the August 2012 upgrades.
  
Line 22: Line 22:
  
 Note on the lib folder naming conventions, the standard in 2012 is to have Note on the lib folder naming conventions, the standard in 2012 is to have
-libraries 64 bit by default, and some 32 bit libraries as well. So my Ubuntu +libraries 64 bit by default, and some 32 bit libraries as well. In Ubuntu 
-12.04 i have the following library folder name convention+12.04 for example, the following library folder name convention is used
   /usr/lib    /usr/lib32   /usr/lib    /usr/lib32
  
 However, on the login node which is little older, its the other way round. The However, on the login node which is little older, its the other way round. The
-lib folder refers to 32 libraries by default, while the lib64 is for 64 bit +lib folder refers to 32 bit libraries by default, while the lib64 is for 64 bit 
-folders. ie its has the following naming convention+libraries. ie its the chpc nodes have the following naming convention
   /usr/lib64    /usr/lib   /usr/lib64    /usr/lib
  
-So when install software, which is 64 bit (default these days) remember you +So when you install software, which is 64 bit (default these days) remember you 
-want to install it the lib64 and the lib folder, as the lib64 folders are +want to install it in the lib64 and not the lib folder, as the lib64 folders are 
-searched first. ie use the following compilation flags +searched first. ie use the following compilation flag --libdir=$HOME/local/lib64
-  --libdir=$HOME/local/lib64+
  
 ===== Setting up the latest GNU binutils and libtool ===== ===== Setting up the latest GNU binutils and libtool =====
Line 349: Line 348:
   $ cp -v $HOME/local/lib64/libp* /tmp/$USER/gcc_build/usr/lib64/    $ cp -v $HOME/local/lib64/libp* /tmp/$USER/gcc_build/usr/lib64/ 
  
-==== GDB : the GNU debugger (optional) ==== 
- 
-  $ download_and_install_from_source.sh \ 
-  http://ftp.gnu.org/gnu/gdb/gdb-7.5.tar.bz2 \ 
-  /tmp/$USER/gcc_build "--libdir=$HOME/local/lib64" $HOME/local 
- 
-Testing took 20 minutes  to complete 
-Got quite a lot of failures here... 
  
  
Line 387: Line 378:
   $ mkdir BUILD   $ mkdir BUILD
   $ cd BUILD   $ cd BUILD
-  $  ../configure --prefix=$HOME/local --disable-cloog-version-check \ 
-   --enable-cloog-backend=isl --libdir=$HOME/local/lib64 
-The following languages will be built: c,c++,fortran,java,lto,objc 
-*** This configuration is not supported in the following subdirectories: 
-     gnattools target-libada target-libgo 
-    (Any other directories should still work fine.) 
- 
-  $ ../configure --prefix=$HOME/local --disable-cloog-version-check \ 
-   --enable-cloog-backend=isl --libdir=$HOME/local/lib64 \ 
-   --with-build-sysroot=/tmp/$USER/usr 
- 
-If this fails going to try  
   $ ../configure --prefix=$HOME/local --disable-cloog-version-check \   $ ../configure --prefix=$HOME/local --disable-cloog-version-check \
    --enable-cloog-backend=isl --libdir=$HOME/local/lib64 \    --enable-cloog-backend=isl --libdir=$HOME/local/lib64 \
Line 406: Line 385:
    --with-ppl-include=$HOME/local/include    --with-ppl-lib=$HOME/local/lib64 \    --with-ppl-include=$HOME/local/include    --with-ppl-lib=$HOME/local/lib64 \
    --with-cloog-include=$HOME/local/include  --with-cloog-lib=$HOME/local/lib64    --with-cloog-include=$HOME/local/include  --with-cloog-lib=$HOME/local/lib64
- +The following languages will be built: c,c++,fortran,java,lto,objc 
 +*** This configuration is not supported in the following subdirectories: 
 +     gnattools target-libada target-libgo 
 +    (Any other directories should still work fine.)
 ===== Compiling GCC ===== ===== Compiling GCC =====
  
Line 440: Line 421:
 ie. //config_debug.c// and rerurn the broken xonfigure command using that ie. //config_debug.c// and rerurn the broken xonfigure command using that
 file. A big help here is to add the -v flag to the xgcc compiler. file. A big help here is to add the -v flag to the xgcc compiler.
- 
-=== could not read symbols: Invalid operation === 
- 
-This error occured when, no setting with gmp path and and with .... 
- 
-=== Bad symbol types === 
-Linking 32 bit libraries against 64 bit libraries... 
  
 ===== Testing ===== ===== Testing =====
Line 537: Line 511:
 folder is selected before your newer version. So to be safe, when you install new folder is selected before your newer version. So to be safe, when you install new
 software, use the following options software, use the following options
-  --prefix=$HOME/local --libdir=$HOME/local/lib64+  /--prefix=$HOME/local --libdir=$HOME/local/lib64
  
 size of install size of install
/app/dokuwiki/data/attic/howto/compiling_gcc.1347869667.txt.gz · Last modified: 2021/12/09 16:42 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
CC Attribution-Noncommercial-Share Alike 3.0 Unported Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki