On Tue, 10 Feb 2015, Dimstar / Dominique Leuenberger wrote:

Hi Richard,

On Tue, 2015-02-10 at 10:51 +0100, Richard Biener wrote:

...

Hi,

we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the openSUSE:Factory:Staging:Gcc49 project. Once that works reasonably I will push GCC 5 to Factory without enabling it as a default - that will be done when it works fully (help appreciated at that point).

There is a porting-to document that explains some issues you may run into (also consider the 4.9 variant as we didn't transition to that): https://gcc.gnu.org/gcc-5/porting_to.html https://gcc.gnu.org/gcc-4.9/porting_to.html

Thanks for the notice! Greatly appreciated. Can you maybe give some quick instructions to the list what a project maintainer can do to get a gcc-5 based are?

I'd like to enable that for example for GNOME:Next, on a special repository, to see how much we break to be able to be prepared for the same (I know some stuff will break - GNOME upstream is already aware of that too). Having some instructions on how to achieve that allows the various project maintainers to get a head start on that.

In theory, if GNOME is fine with what openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX provide, you could set up a repository building against openSUSE:Factory:Staging:Gcc49. Otherwise it's not that easy because C++ dependencies you might have need to be re-built with GCC 5 as the default ABI used for classes like std::string has changed. Richard. -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 02/10/2015, 07:18 PM, Andrei Borzenkov wrote:

В Tue, 10 Feb 2015 10:51:40 +0100 (CET) Richard Biener пишет:

...

Hi,

we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the openSUSE:Factory:Staging:Gcc49 project.

Does it also go through openQA? There was recently report that grub2 built with gcc 4.9 fails in interesting way.

--><-- After some (grub_printf) debugging, I found out that when 'loading' the builtin modules at startup, some modules names are corrupted.

Weird as I have just booted into a system with grub2 built by gcc5. Was this a gcc bug, maybe? Could you retry? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 10 Feb 2015, Cristian Rodríguez wrote:

El 10/02/15 a las 06:51, Richard Biener escribió:

...

Hi,

we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the openSUSE:Factory:Staging:Gcc49 project. Once that works reasonably I will push GCC 5 to Factory without enabling it as a default - that will be done when it works fully (help appreciated at that point).

There is a porting-to document that explains some issues you may run into (also consider the 4.9 variant as we didn't transition to that): https://gcc.gnu.org/gcc-5/porting_to.html https://gcc.gnu.org/gcc-4.9/porting_to.html

You may also find the analysis of Fedora interesting which explains why some packages now fail to build: https://lists.fedoraproject.org/pipermail/devel/2015-February/207549.html

GCC 5 packages can be installed from devel:gcc where they are regularly updated. Those sources also feed openSUSE:Factory:Staging:Gcc49.

Richard.

Cool, thanks for the notice.. I will watch out and fix some build fails if any..in the meanwhile can you or somebody else take a look at this bug ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62249

Short story, LTO has to be disabled when building the systemd package because of this bug, as build checks consider "warning: call to ‘__poll_chk_warn’ declared with attribute warning: poll called with fds buffer too small file nfds entries" a bug and refuse to continue.

It's an "old" bug, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61886, but it looks like hard to fix. I'll push Honza some more... Note that I think we absolutely do _not_ want to build any packages with LTO enabled. Because it's really no fun debugging issues with LTO builds and mind, systemd is of course bug-free.... Thus the proper "fix" for openSUSE is to disable the use of LTO when building packages. Richard. -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg)

On Wed, 11 Feb 2015, Olaf Hering wrote:

On Tue, Feb 10, Richard Biener wrote:

...

we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the openSUSE:Factory:Staging:Gcc49 project. Once that works reasonably I will push GCC 5 to Factory without enabling it as a default - that will be done when it works fully (help appreciated at that point).

Please add "-Werror=date-time" to the global CFLAGS in that project.

Why should I do that and make my life harder? Richard. -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 11 Feb 2015, Olaf Hering wrote:

On Wed, Feb 11, Richard Biener wrote:

...

On Wed, 11 Feb 2015, Olaf Hering wrote:

...

Please add "-Werror=date-time" to the global CFLAGS in that project. Why should I do that and make my life harder?

Makes our life easier, and failures resulting from that change will be fixed quickly.

You can roll your own staging project for that. I have enough FAILs to look at already. Richard. -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Feb 11, 2015 at 12:12:53PM -0300, Cristian Rodríguez wrote:

El 11/02/15 a las 05:23, Olaf Hering escribió:

...

On Tue, Feb 10, Richard Biener wrote:

...

we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the openSUSE:Factory:Staging:Gcc49 project. Once that works reasonably I will push GCC 5 to Factory without enabling it as a default - that will be done when it works fully (help appreciated at that point).

Please add "-Werror=date-time" to the global CFLAGS in that project.

Yes please.. and switch to -fstack-protector-strong instead of -fstack-protector..since fedora releases are already built that way, most "new" crashes in notorius programs have been fixed already but I think it will uncover further bugs that need fixing anyway..

How about we do one thing after the other. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 12/02/15 a las 05:18, Stephan Kulow escribió:

This one we can most likely even have in parallel using gcc48,

You will need a compiler patch for that then.. there is no -fstack-protector-strong in mainline GCC 4.8.. other distributions have backported the feature in.. but for

this I want good test coverage for programs most likely affected within openQA. The times we throw some experiments into the mix and hope for the best are *GONE*.

Cristian, can you come up with some form of a project plan?

Apart from compiling everything with the flag enabled, run the same QA tests, possibly with an additional output check for new "*** stack smashing detected ***" messages I do not see any other way than compile and watch the fallout.. note that chromeOS and Fedora have been compiled with this thing enabled for over a year so most notorius bugs are likely already fixed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Mar 24, 2015 at 8:15 AM, Richard Biener wrote:

pinentry reiserfs memtest86+

I fixed those yesterday.

xen

There is an old xen in that project, the current version in the devel project does not fail. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Mar 25, 2015 at 7:34 AM, Richard Biener wrote:

On Tue, 24 Mar 2015, Cristian Rodríguez wrote:

...

On Tue, Mar 24, 2015 at 8:15 AM, Richard Biener wrote:

...

pinentry reiserfs memtest86+

I fixed those yesterday.

Thanks.

...

...

xen

There is an old xen in that project, the current version in the devel project does not fail.

How did you check? It seems the package in the devel project needs new dependencies not in the current set of packages in openSUSE:Factory:Staging:Gcc49:

Built it with the old compiler plus -std=gnu11 in CFLAGS, unfortunately it seems it was not honoured.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 24 Mar 2015, Richard Biener wrote:

The project to get packages to build with GCC 5 which we should try to transition to has progressed but is not yet finished.

https://build.opensuse.org/project/show/openSUSE:Factory:Staging:Gcc49

currently shows 13 package build fails and 59 packages not built due to failed requirements.

Of the packages that fail building some of them have patches from me either in SR state or just in the devel projects which have not been pushed to Factory.

So we are down to a handful of fails and -><- this close from building DVD images. Main offenders that prevent that are shim -- fixed in devel project but not forwarded to factory :( yast2-auth-server, C++ error, fix sent to maintainers open-lldp -- fixed in devel project but not forwarded to factory :( some fixes are now finally staged and should appear in factory soon (hopefully). Please push your packages to factory. Thanks, Richard. -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, 9 Apr 2015, Marcus Meissner wrote:

On Thu, Apr 09, 2015 at 10:50:07AM +0200, Richard Biener wrote:

...

On Tue, 24 Mar 2015, Richard Biener wrote:

...

The project to get packages to build with GCC 5 which we should try to transition to has progressed but is not yet finished.

https://build.opensuse.org/project/show/openSUSE:Factory:Staging:Gcc49

currently shows 13 package build fails and 59 packages not built due to failed requirements.

Of the packages that fail building some of them have patches from me either in SR state or just in the devel projects which have not been pushed to Factory.

So we are down to a handful of fails and -><- this close from building DVD images. Main offenders that prevent that are

shim -- fixed in devel project but not forwarded to factory :( yast2-auth-server, C++ error, fix sent to maintainers open-lldp -- fixed in devel project but not forwarded to factory :(

some fixes are now finally staged and should appear in factory soon (hopefully).

Please push your packages to factory.

shim might be tricky, this might be the one Microsoft is not willing to sign currently.

Ah, so transitioning to GCC 5 is blocked by Mircosoft? Nice. Richard. -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Apr 09, 2015 at 11:11:10AM +0200, Richard Biener wrote:

Btw, if that is really the case we shouldn't re-build shim all the time. Any minor GCC change can cause different code to be generated and thus require re-signing (or even some random changes in headers).

We will have to change the way we package shim anyway because of new requirements by Microsoft. I already talked to some people about that, but I will have to wait until next week when Stephan Behlert is back from FTO until we can decide this. Johannes -- GPG Key E7C81FA0 EE16 6BCE AD56 E034 BFB3 3ADD 7BF7 29D5 E7C8 1FA0 Subkey fingerprint: 250F 43F5 F7CE 6F1E 9C59 4F95 BC27 DD9D 2CC4 FD66 SUSE LINUX GmbH Maxfeldstraße 5 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)