From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15637] every var expansion in a .pc file prepended with sysroot
Date: Sun, 18 Jun 2023 19:52:39 +0000 [thread overview]
Message-ID: <bug-15637-163-Bl8PC0BoHO@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15637-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15637
--- Comment #2 from stsp <stsp2@yandex.ru> ---
> 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.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-18 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 16:40 [Buildroot] [Bug 15637] New: every var expansion in a .pc file prepended with sysroot bugzilla
2023-06-18 19:35 ` [Buildroot] [Bug 15637] " bugzilla
2023-06-18 19:52 ` bugzilla [this message]
2023-06-18 20:10 ` bugzilla
2024-06-15 15:10 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15637-163-Bl8PC0BoHO@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox