Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#79913 - [rocksdb] pkg-config file incorrectly exports internal CXX_FLAGS

Attached to Project: Arch Linux
Opened by Shanoa Ice (shanoaice) - Wednesday, 11 October 2023, 14:24 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:22 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: rocksdb's pkg-config file incorrectly exports the internal CXX_FLAGS they use in the makefiles, which could got included by consumer build systemd and potentially cause compilation failure / overriden c++_std (there is a -std=c++17 in the exported pkg-config cflags).

A patch is avaliable here: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/rocksdb/pkg-config.patch

Additional info:
* package version(s): 8.5.3 and also the latest release 8.
* link to upstream bug report, if any: https://github.com/facebook/rocksdb/issues/8286

Steps to reproduce:
1. Create a meson project and specify the default cpp_std to be C++20.
2. Declare a dependency on rocksdb.
3. Configure the meson project and examine its generated compile_commands.json and build.ninja. There will most likely be something like `-std=c++20 ... -std=c++17` (irrevelant flags omitted) which cause the prior flag to be overridden.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:22 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/rocksdb/issues/1
Comment by Toolybird (Toolybird) - Wednesday, 11 October 2023, 21:39 GMT
This is an upstream problem i.e. not an Arch packaging issue. Please continue to liaise with upstream to try and get them to fix the problem.

When it comes to patches, Arch really prefers an upstream commit that can be backported...instead of sourcing from some random non-upstream place.

If there is no interest from the PM, this ticket will be closed as "upstream".
Comment by Shanoa Ice (shanoaice) - Thursday, 12 October 2023, 01:25 GMT
I see. I will try to get the upstream maintainer's attention.

Loading...