sys-libs/libcxxrt-0.0_p20170515 stabilization: please add arches if OK. Needed for gcc-6 support.
sure
x86 stabilization stopped due to bug 635528. Please tell me how to proceed.
ping
The current stable version broke my suggested emerge -e @world after switching to the new 17 profile. I will probably not be the only one
(In reply to Jan Vansteenkiste from comment #4) > The current stable version broke my suggested emerge -e @world after > switching to the new 17 profile. I will probably not be the only one Portage 2.3.13 (python 3.5.4-final-0, default/linux/amd64/17.0/desktop, gcc-6.4.0, glibc-2.25-r9, 4.14.2-gentoo x86_64) ================================================================= System uname: Linux-4.14.2-gentoo-x86_64-Intel-R-_Core-TM-_i7-7800X_CPU_@_3.50GHz-with-gentoo-2.4.1 KiB Mem: 32617076 total, 15634272 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Mon, 04 Dec 2017 07:46:39 +0000 Head commit of repository gentoo: 39e713ebd6e4d3d98d13a7a85986a564af8f45e7
(In reply to Jan Vansteenkiste from comment #4) > The current stable version broke my suggested emerge -e @world after > switching to the new 17 profile. I will probably not be the only one Same here. I'm trying tu upgrade to sys-libs/libcxxrt-0.0_p20170515. May I ask why in this version (unlike the previous one), the libunwind useflag is enabled by default ? This break world update when libcxx-3.9.1 is already installed with default configuration : > # emerge -pvuDN world > [ebuild U ~] sys-libs/libcxxrt-0.0_p20170515::gentoo [0.0_p20160922::gentoo] USE="static-libs -libunwind" ABI_X86="32 (64) (-x32)" 60 KiB > > The following USE changes are necessary to proceed: > (see "package.use" in the portage(5) man page for more details) > # required by sys-libs/libcxx-3.9.1::gentoo[libcxxrt] > # required by net-im/discord-bin-0.0.2-r1::gentoo > # required by @coreI3 > # required by @selected > # required by @world (argument) > >=sys-libs/libcxxrt-0.0_p20170515 -libunwind
(In reply to Fab from comment #6) > (In reply to Jan Vansteenkiste from comment #4) > > The current stable version broke my suggested emerge -e @world after > > switching to the new 17 profile. I will probably not be the only one > > Same here. > > I'm trying tu upgrade to sys-libs/libcxxrt-0.0_p20170515. May I ask why in > this version (unlike the previous one), the libunwind useflag is enabled by > default ? This is meant to match the defaults in libcxx-4+. Which is being stabilized as part of bug #637210. Maybe we should combine those two bugs.
Moving amd64 to LLVM stablereq. x86, please stabilize via this bug since you're done with the other one already.
x86 stable Last arch, closing!