commit: 1823d8a300bfe87eb459fc10278d630a1ec37a3d Author: Ben Kohler <bkohler <AT> gentoo <DOT> org> AuthorDate: Fri Jun 7 15:54:04 2019 +0000 Commit: Ben Kohler <bkohler <AT> gentoo <DOT> org> CommitDate: Fri Jun 7 15:54:04 2019 +0000 URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1823d8a3
Remove more obsolete news Ok'd by toolchain team & floppym for python Signed-off-by: Ben Kohler <bkohler <AT> gentoo.org> 2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt | 36 ---------------- ...4-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt | 50 ---------------------- .../2015-07-25-python-targets.en.txt | 26 ----------- 3 files changed, 112 deletions(-) diff --git a/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt b/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt deleted file mode 100644 index 926f6ff..0000000 --- a/2014-06-15-gcc48_ssp/2014-06-15-gcc48_ssp.en.txt +++ /dev/null @@ -1,36 +0,0 @@ -Title: GCC 4.8.3 defaults to -fstack-protector -Author: Ryan Hill <[email protected]> -Content-Type: text/plain -Posted: 2014-06-15 -Revision: 2 -News-Item-Format: 1.0 -Display-If-Installed: >=sys-devel/gcc-4.8.3 -Display-If-Keyword: amd64 -Display-If-Keyword: arm -Display-If-Keyword: mips -Display-If-Keyword: ppc -Display-If-Keyword: ppc64 -Display-If-Keyword: x86 -Display-If-Keyword: amd64-fbsd -Display-If-Keyword: x86-fbsd - -Beginning with GCC 4.8.3, Stack Smashing Protection (SSP) will be -enabled by default. The 4.8 series will enable -fstack-protector -while 4.9 and later enable -fstack-protector-strong. - -SSP is a security feature that attempts to mitigate stack-based buffer -overflows by placing a canary value on the stack after the function -return pointer and checking for that value before the function returns. -If a buffer overflow occurs and the canary value is overwritten, the -program aborts. - -There is a small performance cost to these features. They can be -disabled with -fno-stack-protector. - -For more information these options, refer to the GCC Manual, or the -following articles. - -http://en.wikipedia.org/wiki/Buffer_overflow_protection -http://en.wikipedia.org/wiki/Stack_buffer_overflow -https://securityblog.redhat.com/tag/stack-protector -http://www.outflux.net/blog/archives/2014/01/27/fstack-protector-strong diff --git a/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt b/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt deleted file mode 100644 index d074dbe..0000000 --- a/2014-10-26-gcc_4_7_introduced_new_c++11_abi/2014-10-26-gcc_4_7_introduced_new_c++11_abi.en.txt +++ /dev/null @@ -1,50 +0,0 @@ -Title: GCC 4.7 Introduced the New C++11 ABI -Author: Anthony G. Basile <[email protected]> -Content-Type: text/plain -Posted: 2014-10-26 -Revision: 1 -News-Item-Format: 1.0 -Display-If-Installed: >=sys-devel/gcc-4.7.0 -Display-If-Keyword: amd64 -Display-If-Keyword: arm -Display-If-Keyword: mips -Display-If-Keyword: ppc -Display-If-Keyword: ppc64 -Display-If-Keyword: x86 -Display-If-Keyword: amd64-fbsd -Display-If-Keyword: x86-fbsd - -GCC 4.7 introduced the new experimental 2011 ISO C++ standard [1], along with -its GNU variant. This new standard is not the default in gcc-4.7, 4.8 or 4.9, -the default is still gnu++98, but it can be enabled by passing -std=c++11 or --std=gnu++11 to CXXFLAGS. - -Users that wish to try C++11 should exercise caution because it is not -ABI-compatible with C++98. Nor is C++11 code compiled with gcc-4.7 guaranteed -to be ABI-compatible with C++11 compiled with 4.8, or vice versa [2]. Thus -linking C++98 and C++11, or C++11 compiled with different versions of gcc, is -likely to cause breakage. For packages which are self-contained or do not link -against any libraries written in C++, there is no problem. However, switching -to C++11 and then building packages which link against any of the numerous -libraries in an incompatible ABI can lead to a broken system. - -This is a precautionary news item and the typical user need not do anything. -However, as C++11 gains in popularity and the number of packages using it -increases, it is important that users understand these issues [3]. - -For an ABI compliance checker, and more information about C++ ABIs, see [4]. - -Ref. - -[1] http://www.stroustrup.com/C++11FAQ.html - -[2] Upstream GCC does not support ABI-compatibility between gcc-4.x and 4.y for -any x != y . See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758. Even -having different versions of gcc installed simultaneously may lead to problems, -especially if the older version of gcc is active. An example is -https://bugs.gentoo.org/show_bug.cgi?id=513386. - -[3] Note that some packages like www-client/chromium and net-libs/webkit-gtk -are already using C++11 features. - -[4] http://ispras.linuxbase.org/index.php/ABI_compliance_checker diff --git a/2015-07-25-python-targets/2015-07-25-python-targets.en.txt b/2015-07-25-python-targets/2015-07-25-python-targets.en.txt deleted file mode 100644 index 720eb66..0000000 --- a/2015-07-25-python-targets/2015-07-25-python-targets.en.txt +++ /dev/null @@ -1,26 +0,0 @@ -Title: Python 3.4 enabled by default -Author: Mike Gilbert <[email protected]> -Content-Type: text/plain -Posted: 2015-07-25 -Revision: 1 -News-Item-Format: 1.0 - -Python 3.4 is now enabled by default, replacing Python 3.3 as the -default Python 3 interpreter. - -PYTHON_TARGETS will be adjusted to contain python2_7 and python3_4 by -default via your profile. - -PYTHON_SINGLE_TARGET will remain set to python2_7 by default. - -If you have PYTHON_TARGETS set in make.conf, that setting will still be -respected. You may want to adjust this setting manually. - -Once the changes have taken place, a world update should take care of -reinstalling any python libraries you have installed. You should also -switch your default python3 interpreter using eselect python. - -For example: - -eselect python set --python3 python3.4 -emerge -uDv --changed-use @world
