Right now this is a noop in the former case and a noop in the latter
case unless lang/gcc44 has been installed explicitly.
This puts a bit more emphasis on standardizing on a canonical version
"current" GCC and makes it easier to update that canonical version
by changing the default in Mk/bsd.gcc.mk and updating the lang/gcc port.
That is, USE_GCC=yes means "use a decent/modern version of GCC" without
having to worry about details.
Approved by: portmgr (bdrewery)
used outside of Mk/bsd.gcc.mk) by _GCC_RUNTIME. This is still not
ideal, but at least a documented stopgap, and it avoids the manual
construction of the directory to be added to rpath.
As a side effect, the Makefiles become a tad simpler. On the way,
update to USE_GCC=4.6+ per pending work of linimon and myself.
Approved by: maintainer
Submitted by: gelraen.ua@gmail.com
Reviewed by:
Approved by: gabor (mentor)
Obtained from:
MFC after:
Security:
Feature safe: yes
On some machines resulting binaries contains "/usr/lib" before "/usr/local/lib/gcc45" in rpath and user gets something like
this if tries to launch that binary:
/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.10 required by /usr/local/bin/eiskaltdcpp-gtk not found
Attached patch adds BUILD_DEPENDS on devel/chrpath, which is used to overwrite rpath in built binaries (-DCMAKE_INSTALL_RPATH
only aappends directories to rpath)
