Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
Am Dienstag, 28. November 2017, 12:43:59 CET schrieb Dirkjan Ochtman: > > = > > Title: New 17.0 profiles in the Gentoo repository > > Author: Andreas K. Hüttel> > So gcc-6.4.0 is now in stable on amd64, when do we expect the news item to > land? I was looking at testing the procedure out, but noticed eselect still > doesn't show the 17.0 profiles (I know I can twiddle the symlink instead, > but would like to test the full procedure). Over the next days, likely on the weekend. Just too busy with other (non- gentoo) stuff atm... -a -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, perl, libreoffice) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On Tue, Oct 10, 2017 at 9:16 PM, Andreas K. Huettelwrote: > = > Title: New 17.0 profiles in the Gentoo repository > Author: Andreas K. Hüttel > Posted: xxx > Revision: 1 > News-Item-Format: 2.0 > Display-If-Installed: >=sys-devel/gcc-6.4.0 > So gcc-6.4.0 is now in stable on amd64, when do we expect the news item to land? I was looking at testing the procedure out, but noticed eselect still doesn't show the 17.0 profiles (I know I can twiddle the symlink instead, but would like to test the full procedure). Regards, Dirkjan
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
Am Mittwoch, 11. Oktober 2017, 18:45:37 CEST schrieb Robin H. Johnson: > On Wed, Oct 11, 2017 at 08:10:02AM -0400, Aaron W. Swenson wrote: > > Some of these can take a while. Maybe we want to spell it out: > > > > for p in sys-devel/gcc:6.4.0 sys-devel/binutils sys-libs/glibc; do > > emerge -1 $p || break > > done > > Is gcc-config/binutils-config needed in this sequence as well? I don't think so. Magnus? -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, perl, libreoffice) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
Am Mittwoch, 11. Oktober 2017, 06:41:06 CEST schrieb Walter Dnes: > > 1) Will 6.3.0 be skipped for stabilization? Yes. (Actually I'd prefer to drop it yesterday, but didn't manage to wake up enough toolchain team members for that.) > > 2) If someone decides to override and set "-pie" in USE, will their > current systems continue to function? Yes. (Though technically if you override masked/forced flags you lose your warranty. :) Depending on your system the fallout from 1) switching pie on and 2) *not* rebuilding *world* *may* be rather small. You'll get some spurious link errors, especially when static libraries are involved, and may have to manually rebuild dependencies. If you're willing to deal with that (and promise not to file bugs) ... > On a new install I'll go with > the default, but "emerge -e" takes a long time on my current machine. > It's an ancient 2008 CORE2 with 3 gigs of ram, but it works fine for > me, including Youtube 1080P streaming. -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, perl, libreoffice) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On Wed, Oct 11, 2017 at 07:28:12PM -0400, Brian Evans wrote > It gets forced on with the 17.0 profile. Did you switch yet? Not yet. I'm currently delving further into an obscure ebuild failure for python, so that I can submit a more detailed bug report. Once I get that done (I already have a workaround), I'll look at the profile jump. -- Walter DnesI don't run "desktop environments"; I run useful applications
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On 10/11/2017 04:33 PM, Walter Dnes wrote: > On Wed, Oct 11, 2017 at 12:41:06AM -0400, Walter Dnes wrote > >> I'm on 6.3.0 on x86, which is currently unstable on *ALL* arches, and >> "emerge -pv =sys-devel/gcc-6.3.0" shows "(-pie)". > >And x86 32-bit gcc-6.4.0 shows (-pie) as well... > > == > > [d531][waltdnes][~] ACCEPT_KEYWORDS="~x86" emerge -pv =sys-devel/gcc-6.4.0 > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild NS] sys-devel/gcc-6.4.0:6.4.0::gentoo [6.3.0:6.3.0::gentoo] > USE="cxx fortran nptl openmp sanitize vtv (-altivec) (-awt) -cilk -debug -doc > (-fixed-point) (-gcj) -go -graphite (-hardened) (-jit) (-libssp) -mpx > (-multilib) -nls -objc -objc++ -objc-gc -pch -pgo (-pie) -regression-test > -ssp -vanilla" 74,379 KiB > It gets forced on with the 17.0 profile. Did you switch yet? Brian signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On Wed, Oct 11, 2017 at 12:41:06AM -0400, Walter Dnes wrote > I'm on 6.3.0 on x86, which is currently unstable on *ALL* arches, and > "emerge -pv =sys-devel/gcc-6.3.0" shows "(-pie)". And x86 32-bit gcc-6.4.0 shows (-pie) as well... == [d531][waltdnes][~] ACCEPT_KEYWORDS="~x86" emerge -pv =sys-devel/gcc-6.4.0 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS] sys-devel/gcc-6.4.0:6.4.0::gentoo [6.3.0:6.3.0::gentoo] USE="cxx fortran nptl openmp sanitize vtv (-altivec) (-awt) -cilk -debug -doc (-fixed-point) (-gcj) -go -graphite (-hardened) (-jit) (-libssp) -mpx (-multilib) -nls -objc -objc++ -objc-gc -pch -pgo (-pie) -regression-test -ssp -vanilla" 74,379 KiB -- Walter DnesI don't run "desktop environments"; I run useful applications
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On Wed, Oct 11, 2017 at 08:10:02AM -0400, Aaron W. Swenson wrote: > Some of these can take a while. Maybe we want to spell it out: > > for p in sys-devel/gcc:6.4.0 sys-devel/binutils sys-libs/glibc; do > emerge -1 $p || break > done Is gcc-config/binutils-config needed in this sequence as well? -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Asst. Treasurer E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 signature.asc Description: Digital signature
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On 2017-10-10 21:16, Andreas K. Huettel wrote: > … > Switching involves the following steps: > If not already done, > * Use gcc-config to select gcc-6.4.0 (or later) as system compiler > * Re-source /etc/profile: > . /etc/profile > * Re-emerge libtool Should probably instruct users to upgrade all packages first because it can be, as I’ve experienced, nearly impossible to upgrade GCC if the world isn’t up to the latest stable. An ‘emerge -avuDN world’ should do the trick as a first step. > Then, > * Select the new profile with eselect > * Re-emerge, in this sequence, the selected gcc, binutils, and glibc > emerge -1 sys-devel/gcc:6.4.0 > emerge -1 sys-devel/binutils > emerge -1 sys-libs/glibc Some of these can take a while. Maybe we want to spell it out: for p in sys-devel/gcc:6.4.0 sys-devel/binutils sys-libs/glibc; do emerge -1 $p || break done signature.asc Description: Digital signature
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
> Display-If-Installed: >=sys-devel/gcc-6.4.0 [...snip...] > Switching the profile modifies the use-flags of GCC 6 to generate > PIE executables by default; thus, you need to do the rebuilds > even if you already used GCC 6 beforehand. > > If you do not follow these steps you may get spurious build > failures when the linker tries unsuccessfully to combine non-PIE > and PIE code. > = I'm on 6.3.0 on x86, which is currently unstable on *ALL* arches, and "emerge -pv =sys-devel/gcc-6.3.0" shows "(-pie)". Two questions... 1) Will 6.3.0 be skipped for stabilization? 2) If someone decides to override and set "-pie" in USE, will their current systems continue to function? On a new install I'll go with the default, but "emerge -e" takes a long time on my current machine. It's an ancient 2008 CORE2 with 3 gigs of ram, but it works fine for me, including Youtube 1080P streaming. -- Walter DnesI don't run "desktop environments"; I run useful applications
Re: [gentoo-dev] RFC v2: news item for the 17.0 profiles
On Tue, Oct 10, 2017 at 3:16 PM, Andreas K. Huettelwrote: > = > Title: New 17.0 profiles in the Gentoo repository > Author: Andreas K. Hüttel > Posted: xxx > Revision: 1 > News-Item-Format: 2.0 > Display-If-Installed: >=sys-devel/gcc-6.4.0 > > We have just added a new set of profiles with release version 17.0 > to the Gentoo repository. These bring three changes: > 1) The default C++ language version for applications is now C++14. >This change is mostly relevant to Gentoo developers. It also >means, however, that compilers earlier than GCC 6 are masked >and not supported for use as a system compiler anymore. Feel >free to unmask them if you need them for specific applications. > 2) Where supported, GCC will now build position-independent >executables (PIE) by default. This improves the overall >security fingerprint. The switch from non-PIE to PIE binaries, >however, requires some steps by users, as detailed below. > 3) Up to now, hardened profiles were separate from the default >profile tree. Now they are moving into the 17.0 profile >as a feature there, similar to "no-multilib" and "systemd". > > Please consider switching from your current 13.0 profile to the > corresponding 17.0 profile soon after GCC 6.4.0 has been > stabilized on your architecture. The 13.0 profiles will be deprecated > and removed in the near future. > Can you commit to a deadline on this? Its OK to be wrong (e.g. say 1 month but remove in 3); but "near future" is not actionable by readers. > > Switching involves the following steps: > If not already done, > * Use gcc-config to select gcc-6.4.0 (or later) as system compiler > * Re-source /etc/profile: > . /etc/profile > * Re-emerge libtool > Then, > * Select the new profile with eselect > * Re-emerge, in this sequence, the selected gcc, binutils, and glibc > emerge -1 sys-devel/gcc:6.4.0 > emerge -1 sys-devel/binutils > emerge -1 sys-libs/glibc > * Rebuild your entire system > emerge -e world > > Switching the profile modifies the use-flags of GCC 6 to generate > PIE executables by default; thus, you need to do the rebuilds > even if you already used GCC 6 beforehand. > > If you do not follow these steps you may get spurious build > failures when the linker tries unsuccessfully to combine non-PIE > and PIE code. > = > > > > -- > Andreas K. Hüttel > dilfri...@gentoo.org > Gentoo Linux developer (council, perl, libreoffice)
[gentoo-dev] RFC v2: news item for the 17.0 profiles
= Title: New 17.0 profiles in the Gentoo repository Author: Andreas K. HüttelPosted: xxx Revision: 1 News-Item-Format: 2.0 Display-If-Installed: >=sys-devel/gcc-6.4.0 We have just added a new set of profiles with release version 17.0 to the Gentoo repository. These bring three changes: 1) The default C++ language version for applications is now C++14. This change is mostly relevant to Gentoo developers. It also means, however, that compilers earlier than GCC 6 are masked and not supported for use as a system compiler anymore. Feel free to unmask them if you need them for specific applications. 2) Where supported, GCC will now build position-independent executables (PIE) by default. This improves the overall security fingerprint. The switch from non-PIE to PIE binaries, however, requires some steps by users, as detailed below. 3) Up to now, hardened profiles were separate from the default profile tree. Now they are moving into the 17.0 profile as a feature there, similar to "no-multilib" and "systemd". Please consider switching from your current 13.0 profile to the corresponding 17.0 profile soon after GCC 6.4.0 has been stabilized on your architecture. The 13.0 profiles will be deprecated and removed in the near future. Switching involves the following steps: If not already done, * Use gcc-config to select gcc-6.4.0 (or later) as system compiler * Re-source /etc/profile: . /etc/profile * Re-emerge libtool Then, * Select the new profile with eselect * Re-emerge, in this sequence, the selected gcc, binutils, and glibc emerge -1 sys-devel/gcc:6.4.0 emerge -1 sys-devel/binutils emerge -1 sys-libs/glibc * Rebuild your entire system emerge -e world Switching the profile modifies the use-flags of GCC 6 to generate PIE executables by default; thus, you need to do the rebuilds even if you already used GCC 6 beforehand. If you do not follow these steps you may get spurious build failures when the linker tries unsuccessfully to combine non-PIE and PIE code. = -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, perl, libreoffice) signature.asc Description: This is a digitally signed message part.