New: every var expansion in a .pc file prepended with sysroot
https://bugs.busybox.net/show_bug.cgi?id=15637
Bug ID: 15637
Summary: every var expansion in a .pc file prepended with
sysroot
Product: buildroot
Version: 2023.05
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]Target Milestone: ---
buildroot seems to have some pkg-config wrapper that adds the sysroot path per every variable expansion.
I have a .pc file that emits -rpath on --libs. rpath with the sysroot prefix doesn't work. How should I get the proper rpath with pkg-config under buildroot? Can buildroot be told to not add sysroot path to some variables?
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 15637] every var expansion in a .pc file prepended with sysroot
https://bugs.busybox.net/show_bug.cgi?id=15637
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Yann E. MORIN <[email protected]> --- stsp, All,
Quoted 1 line
buildroot seems to have some pkg-config wrapper that adds the sysroot path per every variable expansion.
Yes and no. Basically, that's pkconf (the pkg-config implementation Buildroot is using) thatadds the sysroot prefix to all variable expansions. The wrapper probided by Buildroot just ensure that the proper sysroot is used.
Quoted 1 line
I have a .pc file that emits -rpath on --libs. rpath with the sysroot prefix doesn't work.
Adding an -rpath link option should not be done in a .pc file; that's rather incorrect.
Furthermore, the RPATH is fixed before assembling the filesystem images, so that only RPATH valid on the targt are present (usually, none is needed); see Makefile line 768.
Regards,
Yann E. MORIN
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 15637] every var expansion in a .pc file prepended with sysroot
In reply to [email protected]https://bugs.busybox.net/show_bug.cgi?id=15637
--- Comment #2 from stsp <[email protected]> ---
Quoted 2 lines
Adding an -rpath link option should not be done in a .pc file; that's rather incorrect.
What would you suggest instead? This is a plugin library for particular program so it doesn't reside in an ldconfig-known location.
I am not aware of any other way than rpath of hardcoding the non-std locations.
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 15637] every var expansion in a .pc file prepended with sysroot
In reply to [email protected]https://bugs.busybox.net/show_bug.cgi?id=15637
--- Comment #3 from stsp <[email protected]> ---
Quoted 1 line
so that only RPATH valid on the targt are present (usually, none is needed);
Maybe it can check if RPATH is
valid on target, by stripping the
sysroot path and checking the result?
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 15637] every var expansion in a .pc file prepended with sysroot
In reply to [email protected]https://bugs.busybox.net/show_bug.cgi?id=15637
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEW |RESOLVED--- Comment #4 from Yann E. MORIN <[email protected]> --- Thank you for your report.
The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues
We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker.
Thank you!
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot