Using newer gcc in /opt/netapps

From LWP-Wiki
Jump to: navigation, search

Gcc-5.2 is in /opt/netapps/gnu/gcc/5.2. In order for you to use it, this may have to be appended to your .profile:


Please note: /opt is *NOT* in, and should not be

The environment variables that are set in the sourceme snippet influence Make-like programs (GNU make, icmake). So projects using such utilities will automatically build your programs using the newer compiler.

If you want to build by calling the compiler directly, you cannot just call 'g++'. Instead, call the newer compiler as $CXX, like this:

${CXX} -o hello

NB: if you are reading this page as a participant (or attendee) of the C++ course, please ask your questions on the mailing list first, not through the Service Desk.

Later versions

You may find that still later versions are available. Check /opt/netapps/gnu/gcc, and alter the above script by adjusting the line



Programs built with this newer compiler and these newer libraries use a newer ABI than the regular compiler/libraries on the LWP. (See )

If you run such programs without the environment settings that were set in the shell snippet, the dynamic linker, at run/load time, will give you relocation errors. Of course it is undesirable to have to set the environment depending on which executables are going to run, even if you can predict that at all.

Luckily, we can hardcode the new library paths into the executable during building:

export LDFLAGS='-Wl,--rpath,/opt/netapps/gnu/gcc/5.2/lib64'

The weird dual-comma syntax means to tell the compiler (-Wl) to tell the linker to use option "--rpath /opt/netapps/gnu/gcc/5.2/lib64".

Such an export command, used just before calling Make, will cause Make to build an executable that will run without any special environment settings, albeit only on the LWP, where the paths mentioned actually exist.