Clarity For Use Of "--sysroot" #2519
Unanswered
vindicatorr
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I get the purpose, but am failing in implementing its use...
I narrowed down my issue to:
/usr/bin/dracut
Success:
Fail:
Success Log:
Fail Log:
So what I'm seeing for "success" is that
dracut@1392
is NOT seeing a path (no$dracutsysrootdir
or$systemdutildir
) when--sysroot
is NOT used, andpkg-config
fills in$systemdutildir
.When
--sysroot
is used, only$dracutsysrootdir
is set, and none of the subsequent checks folow-through to anypkg-config
call.I don't know if I'm supposed to be using the environment variables with
--sysroot
, since some of them say "Optional", but others say they are for sysroot, but don't specify "Optional", but I don't see the value of them likeSYSTEMD_VERSION
.Are they required? What am I missing that the
systemdutildir
isn't being set?EDIT0: I should probably state the reason why I'm pointing to
systemdutildir
is because ofdracut: dracut module 'systemd' will not be installed, because command '/systemd' could not be found!
.EDIT1: Oh god! Is it due to dracut being out-of-date (that the needed stuff doesn't exist in a conf)?
I just saw https://github.com/dracutdevs/dracut/pull/2155/files, noticed the
set_global_var
s, noticed the date for that pull in relation to release-59 (which is what I'm on in Arch Linux).Maybe it'd be nice to get a new release made since we're (sort of?) nearing 1 year since the last release?
EDIT2: Hmm, looking at dracut.conf man, I'm not seeing anything standing out that would apply to getting
systemdutildir
set.Beta Was this translation helpful? Give feedback.
All reactions