Summary: | net-libs/davix-0.8.5 - /.../document.h: error: assignment of read-only member rapidjson::GenericStringRef<CharType>::length | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Guilherme Amadio <amadio> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | csfore |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=914583 https://bugs.gentoo.org/show_bug.cgi?id=919587 https://bugs.gentoo.org/show_bug.cgi?id=924019 |
||
Whiteboard: | fixed in 0.8.5 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 914580 | ||
Attachments: |
emerge-info.txt
emerge-history.txt.xz environment etc.clang.tar.xz etc.portage.tar.xz net-libs:davix-0.8.5:20231206-174702.log qlist-info.txt.xz temp.tar.xz remove const from problematic field applies the commit from upstream to fix gcc 14 |
Description
Toralf Förster
![]() Created attachment 877941 [details]
emerge-info.txt
Created attachment 877942 [details]
emerge-history.txt.xz
Created attachment 877943 [details]
environment
Created attachment 877944 [details]
etc.clang.tar.xz
Created attachment 877945 [details]
etc.portage.tar.xz
Created attachment 877946 [details]
net-libs:davix-0.8.5:20231206-174702.log
Created attachment 877947 [details]
qlist-info.txt.xz
Created attachment 877948 [details]
temp.tar.xz
Created attachment 878597 [details, diff]
remove const from problematic field
I'm not exactly sure if this is best practice but this seems to work, should this be upstreamed or is there a better method about this?
(In reply to Christopher Fore from comment #9) > Created attachment 878597 [details, diff] [details, diff] > remove const from problematic field > > I'm not exactly sure if this is best practice but this seems to work, should > this be upstreamed or is there a better method about this? I'm pretty sure this is the same sort of case as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111544. GCC got stricter. (In reply to Sam James from comment #10) > (In reply to Christopher Fore from comment #9) > > Created attachment 878597 [details, diff] [details, diff] [details, diff] > > remove const from problematic field > > > > I'm not exactly sure if this is best practice but this seems to work, should > > this be upstreamed or is there a better method about this? > > I'm pretty sure this is the same sort of case as > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111544. GCC got stricter. wait, yes, this is bundled rapidjson -> bug 914583 Ah alright, should we use that commit as a patch then until upstream bumps its rapidjson? (In reply to Christopher Fore from comment #12) > Ah alright, should we use that commit as a patch then until upstream bumps > its rapidjson? yes + file another gentoo bug for unbundling rapidjson Created attachment 878598 [details, diff]
applies the commit from upstream to fix gcc 14
Here's the patch from upstream (w/ paths fixed for the package)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6f1a18114dae011613b5bf4c2ab5eaf7b004397 commit f6f1a18114dae011613b5bf4c2ab5eaf7b004397 Author: Guilherme Amadio <amadio@gentoo.org> AuthorDate: 2024-03-10 18:03:59 +0000 Commit: Guilherme Amadio <amadio@gentoo.org> CommitDate: 2024-03-10 18:03:59 +0000 net-libs/davix: fix build with GCC 14, bug 919374 Closes: https://bugs.gentoo.org/919374 Signed-off-by: Guilherme Amadio <amadio@gentoo.org> net-libs/davix/davix-0.8.5.ebuild | 4 ++++ net-libs/davix/files/davix-0.8.5-gcc14.patch | 12 ++++++++++++ 2 files changed, 16 insertions(+) |