safeboot boot loader config #907
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Following commit ed3602f (maintain reproducibility by removing rpath) and applying the same changes for new version of cryptsetup.
* hardcode rpatch patch not needed as `--disable-rpath` is available * remove obsolete config parameters
* use --libdir to fix issue with .la files which had //lib as lib folder * add libblkid as library
If using -I to introduce header files, the elf.h in the target system instead of elf.h shipped with kexec-tools will be included, making its building process failed.
Closed
tlaurion
added a commit
to tlaurion/heads
that referenced
this pull request
May 10, 2021
…boot board being built by CI
This was referenced Aug 24, 2022
Collaborator
|
Abandoned |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The safeboot board configuration is not for a normal coreboot design; it is delivered either as an EFI executable on the local disk or as a PXE image for booting from the network. This means that it does not have the normal size restrictions and can include fancier tools like cryptsetup 2, bash, openssl, etc.