Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use ExtraSearchPaths= when building default tools tree #3290

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

DaanDeMeyer
Copy link
Contributor

Since eba43f0, we always run binaries from ExtraSearchPaths= within the tools tree if one is used. This generally implies the binaries have to be built against the tools tree to be able to run within it. This means that the binaries won't necessarily work when executed on the host, which is the case when building the default tools tree.

To avoid failures when building the default tools tree and using ExtraSearchPaths=, don't use binaries from ExtraSearchPaths= when building the default tools tree.

Since eba43f0, we always run binaries
from ExtraSearchPaths= within the tools tree if one is used. This generally
implies the binaries have to be built against the tools tree to be able to
run within it. This means that the binaries won't necessarily work when
executed on the host, which is the case when building the default tools tree.

To avoid failures when building the default tools tree and using ExtraSearchPaths=,
don't use binaries from ExtraSearchPaths= when building the default tools tree.
@DaanDeMeyer DaanDeMeyer merged commit b5b5846 into systemd:main Dec 20, 2024
28 of 36 checks passed
@DaanDeMeyer DaanDeMeyer deleted the extra-search-paths branch December 20, 2024 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants