Transitioning to GCC 6

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Transitioning to GCC 6

Richard Biener

You may have noticed that GCC 6 packages appeared in Factory (but gcc
used for building packages still points to GCC 5).  Somewhen in
January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
to build packages.  The status of that is that it depends on the
glibc update pending in Staging:B and it still requires fixing a few
packages, mostly -Werror related.  There was a point in time where
openQA was green for x86_64 (and Minimal-X).

Once Staging:B has been accepted I'll formally submit an update
to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
That staging can nevertheless be used to look at the current FAILs
which are

build failed
cluster-glue failed
elfutils failed
espeak failed
gdb failed
jack failed
libyui failed
llvm failed
mozilla-nss failed
pesign failed
python3-base failed
xen failed

and can also be caused by the glibc update which I pulled into
Staging:Gcc6.

Any help is appreciated.

Richard.

--
Richard Biener <[hidden email]>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Normand

On 15/04/2016 13:25, Richard Biener wrote:

>
> You may have noticed that GCC 6 packages appeared in Factory (but gcc
> used for building packages still points to GCC 5).  Somewhen in
> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> to build packages.  The status of that is that it depends on the
> glibc update pending in Staging:B and it still requires fixing a few
> packages, mostly -Werror related.  There was a point in time where
> openQA was green for x86_64 (and Minimal-X).
>
> Once Staging:B has been accepted I'll formally submit an update
> to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
> That staging can nevertheless be used to look at the current FAILs
> which are
>
> build failed
> cluster-glue failed
> elfutils failed
> espeak failed
> gdb failed
> jack failed
> libyui failed
> llvm failed
> mozilla-nss failed
> pesign failed
> python3-base failed
> xen failed
>
> and can also be caused by the glibc update which I pulled into
> Staging:Gcc6.
>
> Any help is appreciated.
>
> Richard.
>

Thanks for the reminder,
The first ppc64le failure I looked at is strange:


"build" package failed because missing rpmlint-Factory on Wed Apr  6 09:52:13 UTC 2016 (2)
but "rpmlint-Factory" build succeeded before           on Tue Apr  5 15:09:30 (3)

Could we have problem of repository update while building ?


(2) https://build.opensuse.org/pa ckage/live_build_log/openSUSE:Factory:Staging:Gcc6/build/standard/ppc64le
(3) https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc6/rpmlint-Factory/standard/ppc64le

--
Michel Normand

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Takashi Iwai
In reply to this post by Richard Biener
On Fri, 15 Apr 2016 13:25:35 +0200,
Richard Biener wrote:

>
>
> You may have noticed that GCC 6 packages appeared in Factory (but gcc
> used for building packages still points to GCC 5).  Somewhen in
> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> to build packages.  The status of that is that it depends on the
> glibc update pending in Staging:B and it still requires fixing a few
> packages, mostly -Werror related.  There was a point in time where
> openQA was green for x86_64 (and Minimal-X).
>
> Once Staging:B has been accepted I'll formally submit an update
> to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
> That staging can nevertheless be used to look at the current FAILs
> which are
>
> build failed
> cluster-glue failed
> elfutils failed
> espeak failed
> gdb failed
> jack failed

jack package failed at the point:

[  411s] ../tests/iodelay.cpp:170:49: error: narrowing conversion of '-1' from '
int' to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
[  411s]  jack_latency_range_t   capture_latency = {-1, -1};
[  411s]                                                  ^

Changing -1 with -1U fixes the problem.

This was a warning beforehand, now it becomes an error.


Takashi
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Richard Biener
On Fri, 15 Apr 2016, Takashi Iwai wrote:

> On Fri, 15 Apr 2016 13:25:35 +0200,
> Richard Biener wrote:
> >
> >
> > You may have noticed that GCC 6 packages appeared in Factory (but gcc
> > used for building packages still points to GCC 5).  Somewhen in
> > January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> > to build packages.  The status of that is that it depends on the
> > glibc update pending in Staging:B and it still requires fixing a few
> > packages, mostly -Werror related.  There was a point in time where
> > openQA was green for x86_64 (and Minimal-X).
> >
> > Once Staging:B has been accepted I'll formally submit an update
> > to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
> > That staging can nevertheless be used to look at the current FAILs
> > which are
> >
> > build failed
> > cluster-glue failed
> > elfutils failed
> > espeak failed
> > gdb failed
> > jack failed
>
> jack package failed at the point:
>
> [  411s] ../tests/iodelay.cpp:170:49: error: narrowing conversion of '-1' from '
> int' to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
> [  411s]  jack_latency_range_t   capture_latency = {-1, -1};
> [  411s]                                                  ^
>
> Changing -1 with -1U fixes the problem.
>
> This was a warning beforehand, now it becomes an error.

Yes, this is due to the change to -std=gnu++14.

Richard.

--
Richard Biener <[hidden email]>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Jan Engelhardt-4
In reply to this post by Takashi Iwai

On Friday 2016-04-15 14:35, Takashi Iwai wrote:

>>[gcc6]
>jack package failed at the point:
>
>[  411s] ../tests/iodelay.cpp:170:49: error: narrowing conversion of '-1' from '
>int' to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
>[  411s]  jack_latency_range_t   capture_latency = {-1, -1};
>[  411s]                                                  ^
>
>Changing -1 with -1U fixes the problem.
>This was a warning beforehand, now it becomes an error.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65801 ?
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Normand
In reply to this post by Richard Biener

On 15/04/2016 13:25, Richard Biener wrote:

>
> You may have noticed that GCC 6 packages appeared in Factory (but gcc
> used for building packages still points to GCC 5).  Somewhen in
> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> to build packages.  The status of that is that it depends on the
> glibc update pending in Staging:B and it still requires fixing a few
> packages, mostly -Werror related.  There was a point in time where
> openQA was green for x86_64 (and Minimal-X).
>
> Once Staging:B has been accepted I'll formally submit an update
> to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
> That staging can nevertheless be used to look at the current FAILs
> which are
>
> build failed
> cluster-glue failed
> elfutils failed
> espeak failed
> gdb failed
> jack failed
> libyui failed
> llvm failed
> mozilla-nss failed
> pesign failed
> python3-base failed
> xen failed
>
> and can also be caused by the glibc update which I pulled into
> Staging:Gcc6.
>
> Any help is appreciated.
>
> Richard.
>

Dinar,

I do not know anything about required bootstrap for Staging setup
but I am impressed by the number of unresolvable for ppc64le archi (1)
(439 entries at time of this email)

Are there missing copy somewhere ?

(1) https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:Gcc6?arch_ppc64le=1&defaults=0&repo_standard=1&unresolvable=1

--
Michel Normand

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Dinar Valeev
On Fri, Apr 15, 2016 at 3:39 PM, Normand <[hidden email]> wrote:

>
> On 15/04/2016 13:25, Richard Biener wrote:
>>
>>
>> You may have noticed that GCC 6 packages appeared in Factory (but gcc
>> used for building packages still points to GCC 5).  Somewhen in
>> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
>> to build packages.  The status of that is that it depends on the
>> glibc update pending in Staging:B and it still requires fixing a few
>> packages, mostly -Werror related.  There was a point in time where
>> openQA was green for x86_64 (and Minimal-X).
>>
>> Once Staging:B has been accepted I'll formally submit an update
>> to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
>> That staging can nevertheless be used to look at the current FAILs
>> which are
>>
>> build   failed
>> cluster-glue    failed
>> elfutils        failed
>> espeak  failed
>> gdb     failed
>> jack    failed
>> libyui  failed
>> llvm    failed
>> mozilla-nss     failed
>> pesign  failed
>> python3-base    failed
>> xen     failed
>>
>> and can also be caused by the glibc update which I pulled into
>> Staging:Gcc6.
>>
>> Any help is appreciated.
>>
>> Richard.
>>
>
> Dinar,
>
> I do not know anything about required bootstrap for Staging setup
> but I am impressed by the number of unresolvable for ppc64le archi (1)
> (439 entries at time of this email)
>
> Are there missing copy somewhere ?
osc ls -b openSUSE:Factory:Staging:Gcc6/_repository/bootstrap_copy/ppc64le
shows binaries. But those are not picked for build in standard
>
> (1)
> https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:Gcc6?arch_ppc64le=1&defaults=0&repo_standard=1&unresolvable=1

>
> --
> Michel Normand
>
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Dominique Leuenberger / DimStar
In reply to this post by Normand
On Fri, 2016-04-15 at 15:39 +0200, Normand wrote:

> On 15/04/2016 13:25, Richard Biener wrote:
> >
> >
> > You may have noticed that GCC 6 packages appeared in Factory (but
> > gcc
> > used for building packages still points to GCC 5).  Somewhen in
> > January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> > to build packages.  The status of that is that it depends on the
> > glibc update pending in Staging:B and it still requires fixing a
> > few
> > packages, mostly -Werror related.  There was a point in time where
> > openQA was green for x86_64 (and Minimal-X).
> >
> > Once Staging:B has been accepted I'll formally submit an update
> > to gcc to make it point to GCC 6 thus obsoleting the above
> > Staging:Gcc6.
> > That staging can nevertheless be used to look at the current FAILs
> > which are
> >
> > build  failed
> > cluster-glue  failed
> > elfutils  failed
> > espeak  failed
> > gdb  failed
> > jack  failed
> > libyui  failed
> > llvm  failed
> > mozilla-nss  failed
> > pesign  failed
> > python3-base  failed
> > xen  failed
> >
> > and can also be caused by the glibc update which I pulled into
> > Staging:Gcc6.
> >
> > Any help is appreciated.
> >
> > Richard.
> >
> Dinar,
>
> I do not know anything about required bootstrap for Staging setup
> but I am impressed by the number of unresolvable for ppc64le archi
> (1)
> (439 entries at time of this email)
>
> Are there missing copy somewhere ?
>
> (1) https://build.opensuse.org/project/monitor/openSUSE:Factory:Stagi
> ng:Gcc6?arch_ppc64le=1&defaults=0&repo_standard=1&unresolvable=1

From what I see the 'root of evil' is with systemd-mini, which is
solvedin TW since today... Not sure if this flowed down into the Gcc6
staging yet.

Cheers,
Dominique
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Cristian Rodríguez-2
In reply to this post by Richard Biener
On Fri, Apr 15, 2016 at 8:25 AM, Richard Biener <[hidden email]> wrote:

>
> You may have noticed that GCC 6 packages appeared in Factory (but gcc
> used for building packages still points to GCC 5).  Somewhen in
> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> to build packages.  The status of that is that it depends on the
> glibc update pending in Staging:B and it still requires fixing a few
> packages, mostly -Werror related.  There was a point in time where
> openQA was green for x86_64 (and Minimal-X).
>
> Once Staging:B has been accepted I'll formally submit an update
> to gcc to make it point to GCC 6

1.will this new version generate PIE executables by default ? (built
with  --enable-default-pie?) Might be worth considering that..
2. Most other distributions are built with fstack-protector-strong by
now.. will the default CFLAGS be changed ?
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Marcus Meissner
On Fri, Apr 15, 2016 at 03:18:32PM -0300, Cristian Rodríguez wrote:

> On Fri, Apr 15, 2016 at 8:25 AM, Richard Biener <[hidden email]> wrote:
> >
> > You may have noticed that GCC 6 packages appeared in Factory (but gcc
> > used for building packages still points to GCC 5).  Somewhen in
> > January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> > to build packages.  The status of that is that it depends on the
> > glibc update pending in Staging:B and it still requires fixing a few
> > packages, mostly -Werror related.  There was a point in time where
> > openQA was green for x86_64 (and Minimal-X).
> >
> > Once Staging:B has been accepted I'll formally submit an update
> > to gcc to make it point to GCC 6
>
> 1.will this new version generate PIE executables by default ? (built
> with  --enable-default-pie?) Might be worth considering that..
> 2. Most other distributions are built with fstack-protector-strong by
> now.. will the default CFLAGS be changed ?

I tried both in staging projects and never quite finished it, as there
was too much fallout.

I can sure reestablish this, but would need help.

Ciao, MArcus
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Cristian Rodríguez-2
On Fri, Apr 15, 2016 at 3:22 PM, Marcus Meissner <[hidden email]> wrote:

> I can sure reestablish this, but would need help.


Well.. If there is an staging project setup I could invest some time
looking at the fallout and see what can I do. ;)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Richard Biener
In reply to this post by Cristian Rodríguez-2
On Fri, 15 Apr 2016, Cristian Rodríguez wrote:

> On Fri, Apr 15, 2016 at 8:25 AM, Richard Biener <[hidden email]> wrote:
> >
> > You may have noticed that GCC 6 packages appeared in Factory (but gcc
> > used for building packages still points to GCC 5).  Somewhen in
> > January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> > to build packages.  The status of that is that it depends on the
> > glibc update pending in Staging:B and it still requires fixing a few
> > packages, mostly -Werror related.  There was a point in time where
> > openQA was green for x86_64 (and Minimal-X).
> >
> > Once Staging:B has been accepted I'll formally submit an update
> > to gcc to make it point to GCC 6
>
> 1.will this new version generate PIE executables by default ? (built
> with  --enable-default-pie?) Might be worth considering that..
No.

> 2. Most other distributions are built with fstack-protector-strong by
> now.. will the default CFLAGS be changed ?

That's sth for the RPM_OPT_FLAGS setting which is outside of GCCs control.

Richard.

--
Richard Biener <[hidden email]>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-buildservice] Re: [opensuse-factory] Transitioning to GCC 6

Dominique Leuenberger / DimStar
In reply to this post by Dominique Leuenberger / DimStar
On Fri, 2016-04-15 at 15:57 +0200, Dominique Leuenberger / DimStar
wrote:

> nar,
> >
> > I do not know anything about required bootstrap for Staging setup
> > but I am impressed by the number of unresolvable for ppc64le archi
> > (1)
> > (439 entries at time of this email)
> >
> > Are there missing copy somewhere ?
> >
> > (1) https://build.opensuse.org/project/monitor/openSUSE:Factory:Sta
> > gi
> > ng:Gcc6?arch_ppc64le=1&defaults=0&repo_standard=1&unresolvable=1
> From what I see the 'root of evil' is with systemd-mini, which is
> solvedin TW since today... Not sure if this flowed down into the Gcc6
> staging yet.

I helped the bootstrapping a little bit - and we are down to 145
unresolvables on ppc64le

The package leading to most failures currently is mozilla-nss, as it
reults poppler not being able to build - and poppler is quite
important.

The 2nd path I see is 'jack' which stops pulseaudio from building.

Cheers,
Dominique

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-packaging] Transitioning to GCC 6

Marcus Meissner
In reply to this post by Cristian Rodríguez-2
On Fri, Apr 15, 2016 at 03:25:12PM -0300, Cristian Rodríguez wrote:
> On Fri, Apr 15, 2016 at 3:22 PM, Marcus Meissner <[hidden email]> wrote:
>
> > I can sure reestablish this, but would need help.
>
>
> Well.. If there is an staging project setup I could invest some time
> looking at the fallout and see what can I do. ;)

I reenabled:
home:msmeissn:stack-protector-strong

I already submitted a fix for libaio.

I also asked for
openSUSE:Factory:Staging:PIE
to be reenabled.

PIE is likely going to need more work, it just needs to be disabled more often.

Ciao, Marcus
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [opensuse-buildservice] Re: [opensuse-factory] Transitioning to GCC 6

Normand
In reply to this post by Dominique Leuenberger / DimStar


On 18/04/2016 14:15, Dominique Leuenberger / DimStar wrote:

> On Fri, 2016-04-15 at 15:57 +0200, Dominique Leuenberger / DimStar
> wrote:
>> nar,
>>>
>>> I do not know anything about required bootstrap for Staging setup
>>> but I am impressed by the number of unresolvable for ppc64le archi
>>> (1)
>>> (439 entries at time of this email)
>>>
>>> Are there missing copy somewhere ?
>>>
>>> (1) https://build.opensuse.org/project/monitor/openSUSE:Factory:Sta
>>> gi
>>> ng:Gcc6?arch_ppc64le=1&defaults=0&repo_standard=1&unresolvable=1
>>  From what I see the 'root of evil' is with systemd-mini, which is
>> solvedin TW since today... Not sure if this flowed down into the Gcc6
>> staging yet.
>
> I helped the bootstrapping a little bit - and we are down to 145
> unresolvables on ppc64le
>
> The package leading to most failures currently is mozilla-nss, as it
> reults poppler not being able to build - and poppler is quite
> important.

mozilla-nss solved by
https://build.opensuse.org/request/show/390595

>
> The 2nd path I see is 'jack' which stops pulseaudio from building.

jack was already solved by
https://build.opensuse.org/request/show/390196

>
> Cheers,
> Dominique
>

--
Michel Normand

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Normand
In reply to this post by Richard Biener

On 15/04/2016 13:25, Richard Biener wrote:
> [CUT] ...
> libyui failed

Seems we would need libyui (1) version 3.2.5 while currently 3.2.4 in devel project (2)
I only added a comment in project.

(1) https://github.com/libyui/libyui/commit/0ad801d0fcf642a5ac736b9659188ce601cac50f
(2) https://build.opensuse.org/package/show/devel:libraries:libyui/libyui



--
Michel Normand

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Jiri Slaby-6
In reply to this post by Richard Biener
On 04/15/2016, 01:25 PM, Richard Biener wrote:
> You may have noticed that GCC 6 packages appeared in Factory (but gcc
> used for building packages still points to GCC 5).  Somewhen in
> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> to build packages.

Could you remove the first hunk from project.diff (copyright year
change) as it breaks the gcc package now?

thanks,
--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Normand
In reply to this post by Richard Biener

On 15/04/2016 13:25, Richard Biener wrote:

>
> You may have noticed that GCC 6 packages appeared in Factory (but gcc
> used for building packages still points to GCC 5).  Somewhen in
> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> to build packages.  The status of that is that it depends on the
> glibc update pending in Staging:B and it still requires fixing a few
> packages, mostly -Werror related.  There was a point in time where
> openQA was green for x86_64 (and Minimal-X).
>
> Once Staging:B has been accepted I'll formally submit an update
> to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
> That staging can nevertheless be used to look at the current FAILs
> [CUT] ...

What are the next actions for gcc6 ? (now that Tumbleweed has been fully rebuilt)
Will we have a new build run of Staging:Gcc6 ?

--
Michel Normand

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Jiri Slaby-6
On 05/02/2016, 08:42 AM, Normand wrote:

>
> On 15/04/2016 13:25, Richard Biener wrote:
>>
>> You may have noticed that GCC 6 packages appeared in Factory (but gcc
>> used for building packages still points to GCC 5).  Somewhen in
>> January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
>> to build packages.  The status of that is that it depends on the
>> glibc update pending in Staging:B and it still requires fixing a few
>> packages, mostly -Werror related.  There was a point in time where
>> openQA was green for x86_64 (and Minimal-X).
>>
>> Once Staging:B has been accepted I'll formally submit an update
>> to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
>> That staging can nevertheless be used to look at the current FAILs
>> [CUT] ...
>
> What are the next actions for gcc6 ?

I think the answer is:
https://build.opensuse.org/request/show/391811

regards,
--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Transitioning to GCC 6

Richard Biener
In reply to this post by Normand
On Mon, 2 May 2016, Normand wrote:

>
> On 15/04/2016 13:25, Richard Biener wrote:
> >
> > You may have noticed that GCC 6 packages appeared in Factory (but gcc
> > used for building packages still points to GCC 5).  Somewhen in
> > January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
> > to build packages.  The status of that is that it depends on the
> > glibc update pending in Staging:B and it still requires fixing a few
> > packages, mostly -Werror related.  There was a point in time where
> > openQA was green for x86_64 (and Minimal-X).
> >
> > Once Staging:B has been accepted I'll formally submit an update
> > to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
> > That staging can nevertheless be used to look at the current FAILs
> > [CUT] ...
>
> What are the next actions for gcc6 ? (now that Tumbleweed has been fully
> rebuilt)
> Will we have a new build run of Staging:Gcc6 ?

The next action is to get SR#391811 into some staging, turning
Staging:Gcc6 into an "official" one (it needs to be re-setup).

I'll be updating the GCC 6 packages which are now in Factory on
a regular schedule (as I notice important bugfixes).

Richard.

--
Richard Biener <[hidden email]>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12