Using newer gcc in /opt/netapps - Revision history

Jurjen at 19:51, 3 September 2023

2023-09-03T19:51:41Z

← Older revision		Revision as of 19:51, 3 September 2023
Line 1:		Line 1:
	[[Category:software-faq]]		[[Category:software-faq]]

	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~~:		Gcc 13.3 is in /opt/netapps/gnu/gcc/13.3. You can use environment modules to use it:

	~~GCCSNIPPET=~~/opt/netapps/gnu/gcc/5.2/~~sourceme~~		module load /opt/netapps/gnu/gcc/13.2.0/modules/gcc-13
	[ -~~r ${GCCSNIPPET} ] && . ${GCCSNIPPET}~~

	Please note: /opt is NOT in ld.so.conf, and should not be		Please note: /opt is NOT in ld.so.conf, 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 hello.cc~~

	~~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 ==		== 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~~		You may find that still later versions are available. Check /opt/netapps/gnu/gcc, and alter the above command accordingly.

	~~GCCBASE="/opt/netapps/gnu/gcc/5~~.2"

	== Addendum ==		== Addendum ==
	Programs built with this newer compiler and these newer libraries use a		Programs built with this newer compiler and these newer libraries may use a
	newer ABI than the regular compiler/libraries on the LWP.		newer ABI than the regular compiler/libraries on the LWP.
	(See		(See
Line 28:		Line 17:

	If you run such programs without the environment settings that were set		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		by the environment module, the dynamic linker, at run/load time, may give
	you relocation errors. ~~Of course it~~ is undesirable to have to set the		you relocation errors. It is undesirable to have to set the
	environment depending on which executables are going to run, even if you		environment depending on which executables are going to run, even if you
	can predict that at all.		can predict that at all.

	Luckily, we can hardcode the new library paths into the executable		Luckily, we can hardcode the new library paths into the executable
	during building:		during building. E.g.:
	export LDFLAGS='-Wl,--rpath,/opt/netapps/gnu/gcc/5.2/lib64'		export LDFLAGS='-Wl,--rpath,/opt/netapps/gnu/gcc/5.2/lib64'

Chris at 15:25, 12 December 2016

2016-12-12T15:25:33Z

← Older revision		Revision as of 15:25, 12 December 2016
Line 20:		Line 20:

	GCCBASE="/opt/netapps/gnu/gcc/5.2"		GCCBASE="/opt/netapps/gnu/gcc/5.2"

			== Addendum ==
			Programs built with this newer compiler and these newer libraries use a
			newer ABI than the regular compiler/libraries on the LWP.
			(See
			https://gcc.gnu.org/onlinedocs/libstdc%2B%2B/manual/using_dual_abi.html )

			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.

Jurjen at 08:41, 1 September 2015

2015-09-01T08:41:01Z

← Older revision		Revision as of 08:41, 1 September 2015
Line 10:		Line 10:
	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.		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++'. ~~Instean~~, call the newer compiler as $CXX, like this:		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 hello.cc		${CXX} -o hello hello.cc

Jurjen at 08:39, 1 September 2015

2015-09-01T08:39:55Z

← Older revision		Revision as of 08:39, 1 September 2015
Line 8:		Line 8:
	Please note: /opt is NOT in ld.so.conf, and should not be		Please note: /opt is NOT in ld.so.conf, and should not be

	~~After sourcing~~ the sourceme, ~~you can call~~ the newer ~~g++ as~~		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.

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

	~~This is what Make commonly does~~, ~~so projects using Makefiles will automatically use~~ the ~~newer compiler~~.		${CXX} -o hello hello.cc

			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 ==		== Later versions ==

Jurjen at 07:54, 1 September 2015

2015-09-01T07:54:59Z

← Older revision		Revision as of 07:54, 1 September 2015
Line 7:		Line 7:

	Please note: /opt is NOT in ld.so.conf, and should not be		Please note: /opt is NOT in ld.so.conf, and should not be

			After sourcing the sourceme, you can call the newer g++ as

			${CXX}

			This is what Make commonly does, so projects using Makefiles will automatically use the newer compiler.

	== Later versions ==		== Later versions ==

Jurjen: The script is not generic, provide a version-specific one in the gcc/5.2 dir

2015-08-18T07:28:08Z

The script is not generic, provide a version-specific one in the gcc/5.2 dir

@@ Line 1: / Line 1: @@
 [[Category:software-faq]]
-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, .bash_profile or whatever applies.
+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 ld.so.conf, and should not be
 == Later versions ==

Jurjen: Snippet failed for 5.2 Now it works

2015-08-18T07:12:00Z

Snippet failed for 5.2 Now it works

← Older revision		Revision as of 07:12, 18 August 2015
Line 1:		Line 1:
	[[Category:software-faq]]		[[Category:software-faq]]
	Gcc-4.~~9.1~~ is in /opt/netapps/gnu/gcc. In order for you to use it, this may have to be appended to your .profile, .bash_profile or whatever applies.
			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, .bash_profile or whatever applies.


	# This is a bash snippet, to be sourced from .profile		# This is a bash snippet, to be sourced from .profile

	GCCBASE="/opt/netapps/gnu/gcc/5.2"		GCCBASE="/opt/netapps/gnu/gcc/5.2"

			LIBDIRS="$(find ${GCCBASE} -iname \\.so\.\ -exec dirname {} \;\|sort \|uniq\|grep -v 32$\|tr '\n' ':')"

	# If you want the newer tools by default, put them at the beginning of $PATH		# If you want the newer tools by default, put them at the beginning of $PATH
Line 13:		Line 17:

	# For good measure: default compiler flags for the C++ course		# For good measure: default compiler flags for the C++ course
	export CXXFLAGS="${CXXFLAGS} -Wall -std=c++11"		export CXXFLAGS="${CXXFLAGS} -Wall -std=c++14"

	# This is for during compile: prefer newer headers		# This is for during compile: prefer newer headers
Line 19:		Line 23:

	# This is for linking during build: prefer newer libraries		# This is for linking during build: prefer newer libraries
	export LD_LIBRARY_PATH="${~~GCCBASE~~}~~/lib/~~.~~./lib64~~:${~~LD_LIBRARY_PATH~~}"		# (with 5.2, this seems to affect run-time)
			export LD_LIBRARY_PATH="${LIBDIRS}:${LD_LIBRARY_PATH}"

			# With 5.2, this affects build time
			export LIBRARY_PATH="${LIBDIRS}:${LIBRARY_PATH}"

	# This is for runtime linking: prefer older libraries		# This is for runtime linking: prefer older libraries
	export LD_RUN_PATH="${LD_RUNPATH}:${GCCBASE}/lib/../lib64"		#export LD_RUN_PATH="${LD_RUNPATH}:${GCCBASE}/lib/../lib64"

	# Man should also find the newer manpages		# Man should also find the newer manpages
	export MANPATH="${MANPATH}:${GCCBASE}/share/man"		export MANPATH="${MANPATH}:${GCCBASE}/share/man"


	Please note: /opt is NOT in ld.so.conf, and should not be		Please note: /opt is NOT in ld.so.conf, and should not be

Jurjen: Fit script to version 5.2

2015-08-17T17:47:45Z

Fit script to version 5.2

← Older revision		Revision as of 17:47, 17 August 2015
Line 4:		Line 4:
	# This is a bash snippet, to be sourced from .profile		# This is a bash snippet, to be sourced from .profile

	GCCBASE="/opt/netapps/gnu/gcc"		GCCBASE="/opt/netapps/gnu/gcc/5.2"

	# If you want the newer tools by default, put them at the beginning of $PATH		# If you want the newer tools by default, put them at the beginning of $PATH
Line 30:		Line 30:


	== ~~GCC-5.0~~ ==		== Later versions ==
	~~There is now (as yet unreleased) GCC-5~~.~~0 as well. You can use~~ the above script~~, but set GCCBASE lie this:~~		You may find that still later versions are available. Check /opt/netapps/gnu/gcc, and alter the above script by adjusting the line

	GCCBASE="/opt/netapps/gnu/gcc/5.0"		GCCBASE="/opt/netapps/gnu/gcc/5.2"

Jurjen at 09:15, 16 February 2015

2015-02-16T09:15:53Z

← Older revision		Revision as of 09:15, 16 February 2015
Line 30:		Line 30:


	There is now ~~Gcc~~-5.0 as well. You can use the above script, but ~~change~~		== GCC-5.0 ==
			There is now (as yet unreleased) GCC-5.0 as well. You can use the above script, but set GCCBASE lie this:
	GCCBASE~~="/opt/netapps/gnu/gcc"~~

	to

	GCCBASE="/opt/netapps/gnu/gcc/5.0"		GCCBASE="/opt/netapps/gnu/gcc/5.0"

	~~Mind you, gcc-5.0 is still in development stage. It hasn't been released yet.~~

Jurjen: Add gcc-5.0

2015-02-16T09:10:09Z

Add gcc-5.0

← Older revision		Revision as of 09:10, 16 February 2015
Line 28:		Line 28:

	Please note: /opt is NOT in ld.so.conf, and should not be		Please note: /opt is NOT in ld.so.conf, and should not be


			There is now Gcc-5.0 as well. You can use the above script, but change

			GCCBASE="/opt/netapps/gnu/gcc"

			to

			GCCBASE="/opt/netapps/gnu/gcc/5.0"

			Mind you, gcc-5.0 is still in development stage. It hasn't been released yet.