Re: [gentoo-dev] Re: Re: stable gcc 5.4.0 ??

2017-04-21 Thread Francesco Riosa
2017-04-21 18:21 GMT+02:00 Jörg Schaible :

> Walter Dnes wrote:
>
> > On Thu, Apr 20, 2017 at 05:52:20PM -0500, Matthias Maier wrote
> >
> >> (A-C) gcc-5.4.0 and gcc-4.9.4 are slotted separately. What is going to
> >> be the default is entirely up to you.
> >
> >   Good to hear.  Like I said, on a fresh install I'd go with the current
> > version (5.4).  But for now, I'll wait for other people to experience
> > problems.  If nothing major, I might switch at a convenient time.
> >
>
>
> You just have to be careful with
>
>  emerge -c
>
> This will remove the old "unused" gcc silently :-/
>

no fear about that issue a:
emerge --select --noreplace sys-devel/gcc:4.9.4
to keep your wanted version of gcc in the world file
(--select is usually already the default)


> Cheers,
> Jörg
>
>
>


[gentoo-dev] Re: Re: stable gcc 5.4.0 ??

2017-04-21 Thread Jörg Schaible
Walter Dnes wrote:

> On Thu, Apr 20, 2017 at 05:52:20PM -0500, Matthias Maier wrote
> 
>> (A-C) gcc-5.4.0 and gcc-4.9.4 are slotted separately. What is going to
>> be the default is entirely up to you.
> 
>   Good to hear.  Like I said, on a fresh install I'd go with the current
> version (5.4).  But for now, I'll wait for other people to experience
> problems.  If nothing major, I might switch at a convenient time.
> 


You just have to be careful with

 emerge -c

This will remove the old "unused" gcc silently :-/

Cheers,
Jörg




Re: [gentoo-dev] Re: Re: stable gcc 5.4.0 ??

2017-04-18 Thread Tomas Mozes
On Tue, Apr 18, 2017 at 3:12 PM, Jörg Schaible <
joerg.schai...@bpm-inspire.com> wrote:

> Tomas Mozes wrote:
>
> [snip]
>
> > As mentioned by others, bugs on packages.gentoo.org will not affect your
> > portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try syncing
> > your portage tree. Don't you have it in your package.mask?
>
> As said, I synced the tree twice this morning (4 hours ago) and the
> KEYWORDS
> in the ebuild do not declare amd64 as stable although it was committed to
> GIT already yesterday. And this is no wonder, because the stable branch of
> the GIT mirror is still not up-to-date:
> https://github.com/gentoo-mirror/gentoo/tree/stable/sys-devel/gcc
>
> gcc-4.5.0-r3 is declared unstable and is not masked.
>
> Cheers,
> Jörg
>
>
>
According to git
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e2be964b72fce0cdb7c16a378b4fa3fa1d37ee38
- the KEYWORDS have amd64 and x86. The github mirror shows the same
https://raw.githubusercontent.com/gentoo-mirror/gentoo/stable/sys-devel/gcc/gcc-5.4.0-r3.ebuild.
Syncing the tree shows the same.

And as such, on a stable system:

# emerge -p gcc
[ebuild  NS] sys-devel/gcc-5.4.0-r3:5.4.0::gentoo [4.9.4:4.9.4::gentoo]
USE="cxx fortran (multilib) nptl openmp sanitize vtv (-altivec) (-awt)
-cilk -debug -doc (-fixed-point) -gcj -go -graphite (-hardened) (-jit)
(-libssp) -mpx -nls -nopie -nossp -objc -objc++ -objc-gc -regression-test
-vanilla" 0 KiB

The git message says it's stable, the bug report also, the mirrors too, so
yes, it is stable now. Maybe check another rsync mirror.


Re: [gentoo-dev] Re: Re: stable gcc 5.4.0 ??

2017-04-18 Thread Aaron W. Swenson
On 2017-04-18 14:27, James Le Cuirot wrote:
> On Tue, 18 Apr 2017 15:12:13 +0200
> Jörg Schaible  wrote:
> 
> > As said, I synced the tree twice this morning (4 hours ago) and the
> > KEYWORDS in the ebuild do not declare amd64 as stable although it was
> > committed to GIT already yesterday. And this is no wonder, because
> > the stable branch of the GIT mirror is still not up-to-date:
> > https://github.com/gentoo-mirror/gentoo/tree/stable/sys-devel/gcc
> 
> It's been held up by this outstanding issue:
> https://qa-reports.gentoo.org/output/gentoo-ci/58d678e2a/output.html#dev-db/psqlodbc

Oh, that’s ridiculous.

I’ve just dropped the particular ebuild that used pgsql-9.1 now.


signature.asc
Description: Digital signature


Re: [gentoo-dev] Re: Re: stable gcc 5.4.0 ??

2017-04-18 Thread James Le Cuirot
On Tue, 18 Apr 2017 15:12:13 +0200
Jörg Schaible  wrote:

> As said, I synced the tree twice this morning (4 hours ago) and the
> KEYWORDS in the ebuild do not declare amd64 as stable although it was
> committed to GIT already yesterday. And this is no wonder, because
> the stable branch of the GIT mirror is still not up-to-date:
> https://github.com/gentoo-mirror/gentoo/tree/stable/sys-devel/gcc

It's been held up by this outstanding issue:
https://qa-reports.gentoo.org/output/gentoo-ci/58d678e2a/output.html#dev-db/psqlodbc

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer



[gentoo-dev] Re: Re: stable gcc 5.4.0 ??

2017-04-18 Thread Jörg Schaible
Tomas Mozes wrote:

[snip]

> As mentioned by others, bugs on packages.gentoo.org will not affect your
> portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try syncing
> your portage tree. Don't you have it in your package.mask?

As said, I synced the tree twice this morning (4 hours ago) and the KEYWORDS 
in the ebuild do not declare amd64 as stable although it was committed to 
GIT already yesterday. And this is no wonder, because the stable branch of 
the GIT mirror is still not up-to-date:
https://github.com/gentoo-mirror/gentoo/tree/stable/sys-devel/gcc

gcc-4.5.0-r3 is declared unstable and is not masked.

Cheers,
Jörg