Summary: | media-plugins/gimp-lqr-0.7.2 : fails to build with -fno-common or gcc-10 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alex.iris.parker, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 705764 | ||
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 logs.tbz2 media-plugins:gimp-lqr-0.7.2:20200206-063240.log temp.tbz2 New ebuild with PATCHES listed Patch including changes from upstream |
Description
Toralf Förster
2020-02-06 22:22:23 UTC
Created attachment 612192 [details]
emerge-info.txt
Created attachment 612194 [details]
emerge-history.txt
Created attachment 612196 [details]
environment
Created attachment 612198 [details]
etc.portage.tbz2
Created attachment 612200 [details]
logs.tbz2
Created attachment 612202 [details]
media-plugins:gimp-lqr-0.7.2:20200206-063240.log
Created attachment 612204 [details]
temp.tbz2
Fixed upstream but I don't think they've released a new source tarball since. I filed a bug asking nicely for a new release with the fixes merged: https://github.com/carlobaldassi/gimp-lqr-plugin/issues/7 (In reply to Alex Parker from comment #8) > Fixed upstream but I don't think they've released a new source tarball > since. I filed a bug asking nicely for a new release with the fixes merged: > > https://github.com/carlobaldassi/gimp-lqr-plugin/issues/7 If they're not up for it, we can apply the patch(es) here? I can prepare a patch with the pull request changes and attach it Created attachment 664111 [details]
New ebuild with PATCHES listed
Created attachment 664114 [details, diff]
Patch including changes from upstream
Builds successfully on GCC 10 with the patch and ebuild I attached :> (In reply to Alex Parker from comment #13) > Builds successfully on GCC 10 with the patch and ebuild I attached :> Thanks! Can you include the GCO sign off in a comment and I can apply these? By making a contribution to this project, I certify that: 1. The contribution was created in whole or in part by me, and I have the right to submit it under the free software license indicated in the file; or 2. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate free software license, and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same free software license (unless I am permitted to submit under a different license), as indicated in the file; or 3. The contribution is a license text (or a file of similar nature), and verbatim distribution is allowed; or 4. The contribution was provided directly to me by some other person who certified 1., 2., 3., or 4., and I have not modified it. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the free software license(s) involved. -- Alexandra Parker (In reply to Sam James from comment #14) > (In reply to Alex Parker from comment #13) > > Builds successfully on GCC 10 with the patch and ebuild I attached :> > > Thanks! Can you include the GCO sign off in a comment and I can apply these? I don't know if I did that right but that's what I found here: https://www.gentoo.org/glep/glep-0076.html#certificate-of-origin (In reply to Alex Parker from comment #16) > (In reply to Sam James from comment #14) > > (In reply to Alex Parker from comment #13) > > > Builds successfully on GCC 10 with the patch and ebuild I attached :> > > > > Thanks! Can you include the GCO sign off in a comment and I can apply these? > > I don't know if I did that right but that's what I found here: > https://www.gentoo.org/glep/glep-0076.html#certificate-of-origin You can include the short version (Signed-off-by: Real Name <email>) but this actually works fine. :) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2e63030ebfbcf3efea6a9a4bffe40acb4df454f commit f2e63030ebfbcf3efea6a9a4bffe40acb4df454f Author: Alexandra Parker <alex.iris.parker@gmail.com> AuthorDate: 2020-10-07 18:27:33 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2020-10-07 18:46:05 +0000 media-plugins/gimp-lqr: fix GCC 10 (-fno-common) build Closes: https://bugs.gentoo.org/708520 Signed-off-by: Alexandra Parker <alex.iris.parker@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> .../files/gimp-lqr-0.7.2-gcc-10-fno-common.patch | 52 ++++++++++++++++++++++ media-plugins/gimp-lqr/gimp-lqr-0.7.2.ebuild | 4 ++ 2 files changed, 56 insertions(+) Thank you! Upstream just released... 0.7.2? Isn't that this version? Anyway, the source tarball is on GitHub and was cut 2 hours ago: https://github.com/carlobaldassi/gimp-lqr-plugin/releases I haven't tried it yet. (In reply to Alex Parker from comment #20) > Upstream just released... 0.7.2? Isn't that this version? Anyway, the source > tarball is on GitHub and was cut 2 hours ago: > > https://github.com/carlobaldassi/gimp-lqr-plugin/releases > > I haven't tried it yet. Uhhh. Oh man. (In reply to Sam James from comment #21) > (In reply to Alex Parker from comment #20) > > Upstream just released... 0.7.2? Isn't that this version? Anyway, the source > > tarball is on GitHub and was cut 2 hours ago: > > > > https://github.com/carlobaldassi/gimp-lqr-plugin/releases > > > > I haven't tried it yet. > > Uhhh. Oh man. I'm so confused. It doesn't build for me with GCC 10. |