LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-09-2017, 10:36 PM   #1
hoodlum7
Member
 
Registered: May 2016
Posts: 30

Rep: Reputation: Disabled
Slackware64-current gcc 7.1.0


Hi all. I have my own personal slackrepo build system up and running for the last year. I have been tracking slackware64-current and my build system for building mythtv has been flawless. However, after the recent upgrade to gcc 7.1.0 I am unable to build mythtv.

I see the following repeatedly before it dies.

/tmp/mythtv/mythtv-0.27.6/mythtv/libs/libmythui/mythdialogbox.h:52: Parse error at "defined"
make[2]: *** [Makefile:524: moc_myththemedmenu.cpp] Error 1


Nothing has changed in the source code. The version is 0.27.6 and has not had an update to the code in 6 months. So, I know it is not a code change

I also tried rebuilding the Qt4 version from Slackware64-current source and it fails as well. I suspect QT and QT based apps are not liking the current version of gcc in Slackware64-current.

Has anyone else seen an issue like this?
 
Old 05-10-2017, 12:55 AM   #2
Reedych
Member
 
Registered: Jul 2016
Location: Earth
Distribution: Slackware64 14.2
Posts: 37

Rep: Reputation: Disabled
I think it's normal because qt package was lastly updated at Wed Sep 21 15:54:06 UTC 2016.
 
Old 05-10-2017, 01:21 AM   #3
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,810

Rep: Reputation: Disabled
Quote:
Originally Posted by hoodlum7 View Post
Hi all. I have my own personal slackrepo build system up and running for the last year. I have been tracking slackware64-current and my build system for building mythtv has been flawless. However, after the recent upgrade to gcc 7.1.0 I am unable to build mythtv.

I see the following repeatedly before it dies.

/tmp/mythtv/mythtv-0.27.6/mythtv/libs/libmythui/mythdialogbox.h:52: Parse error at "defined"
make[2]: *** [Makefile:524: moc_myththemedmenu.cpp] Error 1


Nothing has changed in the source code. The version is 0.27.6 and has not had an update to the code in 6 months. So, I know it is not a code change

I also tried rebuilding the Qt4 version from Slackware64-current source and it fails as well. I suspect QT and QT based apps are not liking the current version of gcc in Slackware64-current.

Has anyone else seen an issue like this?
it's pretty much normal as gcc becomes more and more stricter about the code it accepts.

there has been a jump from version 5.x to version 7.x so these are the changes that developers have to take in account
https://gcc.gnu.org/gcc-6/porting_to.html
https://gcc.gnu.org/gcc-7/porting_to.html

it looks like the mythtv ones already did for their latest stable release as its 0.28.1 version, that uses qt-5.x instead of qt-4.x (so it needs the qt5 package), builds fine here on slackware64-current.

Last edited by ponce; 05-10-2017 at 01:51 AM.
 
Old 05-10-2017, 10:01 AM   #4
hoodlum7
Member
 
Registered: May 2016
Posts: 30

Original Poster
Rep: Reputation: Disabled
I have a build repo I am in the process of getting finished for building MythTV 0.29. I am waiting for Myth to finalize before moving to this repo.

Ponce, Your comments make me wonder if Pat is ever going to go to Qt 5 and the Plasma desktop. I would prefer to use as much official packages as possible.

Thanks for the links. I will see what I can do. I figured I would have to do something with the compiler options. It was getting late for me and decided to see what help I could get via the forums.
 
Old 05-10-2017, 10:10 AM   #5
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,030

Rep: Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697
Quote:
Originally Posted by hoodlum7 View Post
Ponce, Your comments make me wonder if Pat is ever going to go to Qt 5 and the Plasma desktop. I would prefer to use as much official packages as possible.
I imagine this is going to occur this development cycle, especially since KDE4 is no longer developed. Eric already has working Plasma 5 packages in his ktown repo, so it will just be a matter of Pat making the decision to switch.
 
Old 05-10-2017, 12:52 PM   #6
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,648

Rep: Reputation: Disabled
Not to hijack this thread, but some other examples of gcc 7.1.0 issues are...

1. bsnes-mercury and bsnes-libretro get stuck indefinitely on the following command with '-O3' which is default in the Makefile and upstream higan doesn't remotely compile anymore although that was rather broken to begin with.
Code:
cc1plus -quiet -I . -D_GNU_SOURCE -D SFC_LAGFIX -D __LIBRETRO__ -D GIT_VERSION=" 608801c" -D PROFILE_ACCURACY sfc/ppu/ppu.cpp -quiet -dumpbase ppu.cpp -mtune=generic -march=x86-64 -auxbase-strip obj/sfc-ppu-accuracy.o -O3 -std=gnu++11 -fomit-frame-pointer -fPIC -o /tmp/cc9TWEsc.s
https://github.com/libretro/bsnes-mercury/issues/47

2. pcsx2 was hit especially hard and now segfaults when opening various menus in the frontend.

https://github.com/PCSX2/pcsx2/issues/1935

3. The OpenGL gsdx plugin is also entirely non-functional...

https://github.com/PCSX2/pcsx2/issues/1937
 
1 members found this post helpful.
Old 05-10-2017, 12:57 PM   #7
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,497

Rep: Reputation: 1115Reputation: 1115Reputation: 1115Reputation: 1115Reputation: 1115Reputation: 1115Reputation: 1115Reputation: 1115Reputation: 1115
This makes me think I should test some of the stuff I've written with this new gcc version.
 
1 members found this post helpful.
Old 05-10-2017, 05:58 PM   #8
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,974

Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
GCC 7.1.0 is currently used only in a small number of distributions so not all projects are tested with the new GCC. So far, only LFS, Fedora, Ubuntu Snapshot, and Gentoo Unstable that have shipped GCC 7.1.0 besides Slackware-Current.

It will take time before other projects can catch up with the GCC latest release.
 
Old 05-10-2017, 08:43 PM   #9
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
Quote:
Originally Posted by willysr View Post
It will take time before other projects can catch up with the GCC latest release.
You pointed exactly WHY a distribution should NOT ship the latest mightiest GCC release.

Just because will take time before other projects can catch up with the GCC latest release.
 
Old 05-10-2017, 08:47 PM   #10
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
Quote:
Originally Posted by bassmadrigal View Post
I imagine this is going to occur this development cycle, especially since KDE4 is no longer developed. Eric already has working Plasma 5 packages in his ktown repo, so it will just be a matter of Pat making the decision to switch.
I hope NOT, especially while KDE4 could be patched.
 
Old 05-10-2017, 09:14 PM   #11
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,030

Rep: Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697Reputation: 3697
Quote:
Originally Posted by Darth Vader View Post
You pointed exactly WHY a distribution should NOT ship the latest mightiest GCC release.

Just because will take time before other projects can catch up with the GCC latest release.
Guess what, Slackware-current is a development branch. It isn't to be used in a production environment where these gcc issues can bite you. Hopefully by the time the next stable is released, gcc7 support in 3rd-party projects will have matured.

Quote:
Originally Posted by Darth Vader View Post
I hope NOT, especially while KDE4 could be patched.
Yeah, but who's going to do the patching? XFree86 can be patched too, but nobody's doing it.
 
6 members found this post helpful.
Old 05-10-2017, 09:36 PM   #12
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
Quote:
Originally Posted by bassmadrigal View Post
Guess what, Slackware-current is a development branch. It isn't to be used in a production environment where these gcc issues can bite you. Hopefully by the time the next stable is released, gcc7 support in 3rd-party projects will have matured.
The bad news is that Slackware have the habit to stay on top version of GCC until last minute, so your claim does not apply...


Quote:
Originally Posted by bassmadrigal View Post
Yeah, but who's going to do the patching? XFree86 can be patched too, but nobody's doing it.
Overall, I believe that could help lurking to what CentOS do, instead to look to Arch Linux like a fanboy to a Rock Star...

Last edited by Darth Vader; 05-10-2017 at 09:39 PM.
 
Old 05-10-2017, 09:49 PM   #13
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,974

Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
I believe when the next Slackware gets released, GCC is tamed
We haven't heard Patrick calling for Beta 1. Even with Beta 1 announced, the final released is still months away (14.2 was released about 5 months after Beta 1 was announced).

What matters is that core packages are correctly built because that will be the base for third party packages or repository such as SBo or any other personal repositories.

As for KDE 4, with more and more packages are being ported to KDE 5, using KDE 4 for next release which will be supported for at least 5 years is not the best idea. People who wanted to keep using KDE 4 can still be using Slackware 14.2. It's their choice. No one is forcing users to migrate to newer version of Slackware every time a new release is available.
 
2 members found this post helpful.
Old 05-10-2017, 10:03 PM   #14
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
Quote:
Originally Posted by willysr View Post
No one is forcing users to migrate to newer version of Slackware every time a new release is available.
Now I use Slackware 14.1 for stable uses, current for playing with. Hoping that I can use 14.3, through...
 
Old 05-10-2017, 10:06 PM   #15
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,974

Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
We are not sure whether the next version will be called 14.3 or 15.0 or probably jump to another version. I guess we will have to wait for that
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can I grab Slackware64-current's gcc moisespedro Slackware 5 05-22-2015 01:24 PM
Slackware64 current without gcc compiler after installing multilibs MattFly Slackware 7 05-18-2015 10:48 AM
Slackware64 current gcc-4.8.1 and glibc-2.17 tuxbg Slackware 79 05-02-2014 12:35 PM
Slackware64 -current (multilib) -- Wrong GCC version slaka Slackware 2 05-13-2013 10:39 AM
slackware64-current libtool using path to old version of GCC JazzItSelf Slackware 6 11-21-2011 11:35 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration