Today's GCC 9.1 update. Does it break anything?

Lockywolf · 05-04-2019, 12:26 AM

I found that the recent -current has updated GCC with a major version bump (along with a new option in LLVM, thanks, Patrick Volkerding!).

Does it break much? I have some important stuff on my machine compiled with GCC 5, so that shouldn't matter much, but as far as I remember, C++ (NOT pure C) doesn't guarantee linking compatibility even between different major versions of the same compiler.

Should I wait for glibc and friends to be recompiled with GCC 9, or just roll the update on?

Fat_Elvis · 05-04-2019, 12:45 AM

This is a relevant question. I'd like to know as well.

LuckyCyborg · 05-04-2019, 12:47 AM

deleted

_gin · 05-04-2019, 12:57 AM

Did we get the D language support (gcd), I don't see It in the SlackBuild?

3rensho · 05-04-2019, 01:39 AM

Running Slack64-current with latest Plasma5 and so far everything I have run has worked fine since I built 9.1 yesterday.

nobodino · 05-04-2019, 01:54 AM

I am trying to rebuild SFS with the new gcc. Wait and see.

Didier Spaier · 05-04-2019, 02:05 AM

Quote:

Originally Posted by 3rensho

Running Slack64-current with latest Plasma5 and so far everything I have run has worked fine since I built 9.1 yesterday.

gcc is used to compile stuff, not to run it.

volkerdi · 05-04-2019, 02:09 AM

Quote:

Originally Posted by Didier Spaier

gcc is used to compile stuff, not to run it.

A little of each, really. The gcc-g++ package supplies libstdc++.so.6, for example. But with the versioned symbols that have been in use for a long time, it's unlikely that a newer libstdc++ will break anything.

Lockywolf · 05-04-2019, 02:59 AM

Quote:

Originally Posted by _gin

Did we get the D language support (gcd), I don't see It in the SlackBuild?

Don't think so. I don't find it on my system.

Well, I did update the system after all, and everything seems to be working okay.

3rensho · 05-04-2019, 03:07 AM

Quote:

gcc is used to compile stuff, not to run it.

I realize that Didier. What I meant is other programs are still running fine having been compiled with an earlier version of gcc. That has not always been the case with earlier versions of gcc.

Lockywolf · 05-04-2019, 04:10 AM

Woops.

My Konqueror broke down.

Quote:

There was an error loading the module WebKit.
The diagnostics is:
Cannot load library /usr/lib64/kde4/kwebkitpart.so: (/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /usr/lib64/libQtWebKit.so.4))

3rensho · 05-04-2019, 05:48 AM

Just tried my Konqueror and it works fine.

mlangdn · 05-04-2019, 06:02 AM

When re-installing the nvidia blob, it complained that the kernel was compiled with the previous version of gcc. I told it to go ahead and everything is fine.

Didier Spaier · 05-04-2019, 06:08 AM

Quote:

Originally Posted by volkerdi

A little of each, really. The gcc-g++ package supplies libstdc++.so.6, for example. But with the versioned symbols that have been in use for a long time, it's unlikely that a newer libstdc++ will break anything.

I stand corrected, thanks for the heads-up.

Olek · 05-04-2019, 06:34 AM

After update my KDE can't start. It dies on first icon (disk) and return to login window.
Hopefully XFCE works.