From: <Paul_Koning@Dell.com>
To: <gdb@sourceware.org>
Subject: sysroot and softlinks
Date: Wed, 04 Nov 2015 14:56:00 -0000 [thread overview]
Message-ID: <736EC98D-ED8D-4179-B82A-984C249E1D8E@dell.com> (raw)
I have a cross-build setup where the target file system image is built into some directory tree, which means that the base of that tree is the value to be used in "set sysroot".
For the most part that works. But I have a reference to a file (shared library or the like) which is actually a softlink, and the link target is an absolute path. That absolute path is valid in the target system, but not in the sysroot subtree.
Changing that softlink to a relative link would cure the problem, of course, but I don't really want to mess with the system build; for one thing, that wouldn't help with previously built images.
The other solution would be for solid_find to test for this case: check if the name is a softlink and if so, whether its target is absolute. If yes, prefix sysroot onto the target and repeat.
Does that change make sense?
paul
next reply other threads:[~2015-11-04 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 14:56 Paul_Koning [this message]
2015-11-04 15:15 ` Andreas Schwab
2015-11-04 15:58 ` Paul_Koning
2015-11-04 16:48 ` Jan Kratochvil
2015-11-04 16:57 ` Paul_Koning
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=736EC98D-ED8D-4179-B82A-984C249E1D8E@dell.com \
--to=paul_koning@dell.com \
--cc=gdb@sourceware.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