| Summary: | Double slash in file generated by ecm_generate_pkgconfig_file | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] extra-cmake-modules | Reporter: | Steve Cossette <farchord> |
| Component: | general | Assignee: | ecm-bugs-null <ecm-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Cannot reproduce in my local build. I get "libdir=${prefix}/lib64"
Can you give your exact CMake arguments?
Hopefully this is what you're asking: + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rp> + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/> + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened> + export FFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-pack> + export LDFLAGS + /usr/bin/cmake -S . -B redhat-linux-build -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DBUILD_SHARED_LIBS:BOOL=ON -DB> Can you also give the full content of /usr/lib64/pkgconfig/KF6WaylandClient.pc ? Does this also happen with kf5-kwayland (or any KF5 package)? *** Bug 474701 has been marked as a duplicate of this bug. *** (In reply to Nicolas Fella from comment #4) > Does this also happen with kf5-kwayland (or any KF5 package)? Yes, kf6-bluez-qt (We're working on packaging more kf6 packages and we're two packagers doing this so there may be more) (In reply to Nicolas Fella from comment #3) > Can you also give the full content of > /usr/lib64/pkgconfig/KF6WaylandClient.pc ? prefix=/usr exec_prefix=${prefix} libdir=${prefix}//usr/lib64 includedir=/usr/include/KF6/KWayland Name: KF6WaylandClient Description: Qt-style API to interact with the wayland-client API URL: https://www.kde.org/ Version: 5.240.0 Libs: -L${prefix}//usr/lib64 -lKF6WaylandClient Cflags: -I/usr/include/KF6/KWayland Requires: Qt6Gui (In reply to Steve Cossette from comment #6) > (In reply to Nicolas Fella from comment #4) > > Does this also happen with kf5-kwayland (or any KF5 package)? > > Yes, kf6-bluez-qt (We're working on packaging more kf6 packages and we're > two packagers doing this so there may be more) I wanted to know about KF*5* But I can answer that myself. /usr/lib64/pkgconfig/KF5WaylandClient.pc also shows this, so it's not a new problem. That makes sense, because the relevant code didn't change (In reply to Nicolas Fella from comment #9) > But I can answer that myself. /usr/lib64/pkgconfig/KF5WaylandClient.pc also > shows this, so it's not a new problem. That makes sense, because the > relevant code didn't change My bad. I'm not entirely sure what's happening. In particular I'm wondering what the value of KDE_INSTALL_LIBDIR/CMAKE_INSTALL_LIBDIR is, but I don't see that being set to anything in your flags. *maybe* https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/268 fixes the issue (In reply to Nicolas Fella from comment #11) > I'm not entirely sure what's happening. In particular I'm wondering what the > value of KDE_INSTALL_LIBDIR/CMAKE_INSTALL_LIBDIR is, but I don't see that > being set to anything in your flags. > > *maybe* > https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/268 > fixes the issue KDE_INSTALL_LIBDIR = /usr/lib64 The other, I actually don't know to be honest. I've asked around and CMAKE_INSTALL_LIBDIR is set on it's own, we don't set it > KDE_INSTALL_LIBDIR = /usr/lib64 ah, that makes sense. the value is absolute, so the problem should be indeed fixed with https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/268 |
Good afternoon! We're working on bringing kf6 packages into Fedora. For this package, we get the following error: kf6-kwayland-devel.x86_64: E: double-slash-in-pkgconfig-path /usr/lib64/pkgconfig/KF6WaylandClient.pc libdir=${prefix}//usr/lib64 kf6-kwayland-devel.x86_64: E: double-slash-in-pkgconfig-path /usr/lib64/pkgconfig/KF6WaylandClient.pc Libs: -L${prefix}//usr/lib64 -lKF6WaylandClient Here's the error description: double-slash-in-pkgconfig-path: This pkg-config file contains a path with a double slash ('//') in it. This will break debugedit when stripping debug symbols during package building if these paths have been passed to gcc, and fail with the following error: canonicalization unexpectedly shrank by one character. This is after building commit 770e361d9b6521191e4464944e49b41b21ccdf2e (Latest at the time of speaking): https://invent.kde.org/frameworks/kwayland/-/commit/770e361d9b6521191e4464944e49b41b21ccdf2e If you need any kind of information please do not hesitate to ask! Thanks!