Issue #16836 has been updated by nobu (Nobuyoshi Nakada). Status changed from Assigned to Feedback IIRC, `rpath` is the path embedded in the linked binary, in order to resolve shared libraries at runtime. There is no reason to set the path that won’t exist at runtime, I think. ---------------------------------------- Bug #16836: configure-time LDFLAGS leak into ruby pkg-config file https://bugs.ruby-lang.org/issues/16836#change-100690 * Author: stapelberg (Michael Stapelberg) * Status: Feedback * Priority: Normal * Assignee: nobu (Nobuyoshi Nakada) * ruby -v: 2.7.1 * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- When building ruby with e.g. `-Wl,-rpath=/ro/ruby-amd64-2.7.1-6/lib` (to make it hermetic, see my work-in-progress post at https://website-review.zekjur.net/pull/hermetic/posts/2020-05-04-distri-herm...), I noticed that the resulting pkg-config file (`lib/pkgconfig/ruby-2.7.pc`) includes the LDFLAGS! This will result in software that links against ruby being built with the wrong `rpath`. In general, LDFLAGS should not be persisted into pkg-config. The attached patch fixes the issue. Thanks, ---Files-------------------------------- pc-ldflags.patch (563 Bytes) -- https://bugs.ruby-lang.org/