Summary: | app-misc/spacenavd-0.6 : fails to build with -fno-common or gcc-10 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Sebastian Pipping <sping> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | thomas |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/FreeSpacenav/spacenavd/issues/17 | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=707734 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 705764 | ||
Attachments: |
emerge-info.txt
app-misc:spacenavd-0.6:20200128-145525.log emerge-history.txt environment etc.portage.tbz2 temp.tbz2 Patch to fix compilation with -fno-common |
Description
Toralf Förster
2020-01-28 18:50:38 UTC
Created attachment 606888 [details]
emerge-info.txt
Created attachment 606890 [details]
app-misc:spacenavd-0.6:20200128-145525.log
Created attachment 606892 [details]
emerge-history.txt
Created attachment 606894 [details]
environment
Created attachment 606896 [details]
etc.portage.tbz2
Created attachment 606898 [details]
temp.tbz2
Created attachment 609508 [details, diff]
Patch to fix compilation with -fno-common
This patch should work. Could someone else test it?
Let's discuss that with upstream at https://github.com/FreeSpacenav/spacenavd/issues/17 so that we patch in a way that is future proof. (In reply to Thomas Albers from comment #7) > Created attachment 609508 [details, diff] [details, diff] > Patch to fix compilation with -fno-common > > This patch should work. Could someone else test it? Hi Thomas, upstream does not like this direction for a patch, see https://github.com/FreeSpacenav/spacenavd/issues/17#issuecomment-580949667 . Their takes is https://github.com/FreeSpacenav/spacenavd/commit/081182f1675bb69eec58d92698f1ba2f23466d3f which I'll be applying now (so that we don't have to forward-port a patch for every new release). Still, thank you for making and sharing that patch! The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d59da78d876aba0d7c867ed2083c51489ad80908 commit d59da78d876aba0d7c867ed2083c51489ad80908 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2020-01-31 23:36:57 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2020-01-31 23:42:51 +0000 app-misc/spacenavd: Support GCC 10 Closes: https://bugs.gentoo.org/706966 Signed-off-by: Sebastian Pipping <sping@gentoo.org> Package-Manager: Portage-2.3.84, Repoman-2.3.20 app-misc/spacenavd/files/spacenavd-0.7-gcc10.patch | 24 ++++++++++++++++++++++ app-misc/spacenavd/spacenavd-0.7.ebuild | 4 ++++ 2 files changed, 28 insertions(+) The upstream fix might be applied to spacenavd-0.6 as well, mightn't it? (In reply to Thomas Albers from comment #11) > The upstream fix might be applied to spacenavd-0.6 as well, mightn't it? I'll take that as an explicit wish, give me a second. I didn't apply to 0.6 originally, because it is marked as stable, touching stable ebuilds is risky, and making a patch 0.6-r1 seems to have little value while we have 0.7 around and no explicit wish earlier. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bff35faa79ba247ccbb7532ed4809035dbe5a22b commit bff35faa79ba247ccbb7532ed4809035dbe5a22b Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2020-02-01 19:51:56 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2020-02-01 19:53:07 +0000 app-misc/spacenavd: Support GCC 10 Bug: https://bugs.gentoo.org/706966 Signed-off-by: Sebastian Pipping <sping@gentoo.org> Package-Manager: Portage-2.3.84, Repoman-2.3.20 app-misc/spacenavd/spacenavd-0.6.ebuild | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) |