From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Request for comments: CROSS_LIB_DIR handling etc.
Date: Wed, 13 Oct 2021 09:29:24 +0200 [thread overview]
Message-ID: <4d8f168a-d731-8cc0-892c-19c9f0cdc879@t2data.com> (raw)
Hello.
I've been correcting various hardcoded paths in ptxdist packages and
whatnot lately. This started with ptxdist not coping well with
toolchains that adhere to the ABI path for various architectures.
Yesterday, I dug into the problem that on x86_64 (/lib64), all .pc.in ->
.pc file transformations looked broken with hardcoded paths. At first I
thought it had something to do with autoconf or pkg-config but after a
while I found this.
scripts/lib/ptxd_make_world_install_mangle_pc.awk
Which after a while made me realize that there is still a lot of code in
ptxdist core stuff that assumes that lib-paths are only /lib and nothing
else.
So. I'm presenting a two options here.
1. Fix all ptxdist core stuff, because really, ptxdist should be more
flexible than hardcoded paths. Esp. for libs.
2. Split ptxd_get_lib_dir, because, ld.so path should not be assumed to
be the same as main library install path. So ptxd_get_ld_lib_dir which
does what it does today and install ld there and ptxd_get_lib_dir = /lib
and be done with all the userspace library transformations.
So. Number one probably requires a lot of more work and a lot of
headache. Number two should be rather straightforward, atleast in theory.
Any thoughts?
/Christian
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-10-13 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 7:29 Christian Melki [this message]
2021-10-15 13:12 ` Michael Olbrich
2021-10-15 13:34 ` Christian Melki
2021-11-04 10:06 ` Christian Melki
2021-11-05 8:57 ` Michael Olbrich
2021-11-05 9:31 ` Christian Melki
2023-03-23 5:59 ` Michael Olbrich
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=4d8f168a-d731-8cc0-892c-19c9f0cdc879@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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