-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AfterStep git 2015-02-13 FTBFS w/Fedora 22 #7
Comments
Hi Jeff,
Two quick questions:
1) Does this same process work on a less recent release of Fedora or
also bails out with the same error?
2) Is this the 2.2.12 release, or is it the latest on github? If the
latter, is it from sashavasko/afterstep-devel or Remmy/afterstep?
|
Remmy: I had a heavily-patched (brought-up to cvs/git) version of 2.2.12 that I grabbed the latest from github of Sasha's master; the last commit on his For grins, I tried building the 2.2.12 version of AS "as-is", and got the Every time gcc updates to a newer version, it's less and less forgiving; Jeff On Wed, May 13, 2015 at 3:58 AM, Remco Rijnders notifications@github.com
|
It appears gcc 5.1.1 doesn't like "inline" statements, or is VERY particular about how they are used. I've forwarded you a patch stripping out "inline" from statements in 52 files. AS now appears to build under Fedora 22 and gcc 5.1.1. Plenty of warnings, but a build all the same. I'll need to do more testing, but I'm happy thus far. Enjoy. |
AfterStep git 2015-02-13 FTBFS under Fedora 22 Beta, gcc version 5.1.1.
Sent tarball of build log generated with "script" command to your email.
The text was updated successfully, but these errors were encountered: