Go to file
Yann E. MORIN 3f7e96a01a package/mender-grubenv: fix install for legacy BIOS or ARM U-Boot
Some last-minute changes were made when applying commits 7a68960b68
(boot/grub2/Config.in: add symbols to represent legacy and EFI boot) and
4d5b209384 (package/mender-grubenv: fix grub module checks), and the
renaming of the BR2_TARGET_GRUB_LEGACY was not fully propagated.

This caused the path to the boot files to always be interpreted as being
the EFI one, and never the legacy one. In practice, that was not causing
any build failure, because the path was passed at build-time to
mender-grubenv, that would use it as the location where to install its
files, and finally as the location where our image-isntall commands
would look for them.

Still this is incorrect because it would not match where grub2 would
eventually end up lookig for its files at runtime...

To avoid further issue, drop the conditional block dedicated to setting
the path to the boot files, drop the intermediate variable, and move
setting the environment variable down into the existing conditional
block.

We do drop the intermediate variable, because there is no longer any
genericity needed: the installation commands are already duplicated for
the two cases anyway.

Reported-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Adam Duskett <aduskett@gmail.com>
Cc: Köry Maincent <kory.maincent@bootlin.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-12-05 12:26:34 +01:00
arch arch/config: Make RISC-V 64-bits MMU optional 2021-10-27 14:39:01 +02:00
board configs/zynqmp_zcu106: fix arm-trusted-firmware build failure 2021-11-21 21:53:42 +01:00
boot boot/grub2/Config.in: add symbols to represent legacy and EFI boot 2021-12-04 18:04:08 +01:00
configs configs/nitrogen8mp: update device trees list 2021-11-21 21:55:45 +01:00
docs docs/manual: use single space in LIBFOO_{DEVICES, PERMISSIONS} 2021-12-02 18:11:50 +01:00
fs fs/ext2: fir (again) namespace for variables 2021-10-13 18:01:34 +02:00
linux {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.{4, 10, 15}.x series 2021-12-03 08:55:49 +01:00
package package/mender-grubenv: fix install for legacy BIOS or ARM U-Boot 2021-12-05 12:26:34 +01:00
support support/dependencies: avoid spurious warning on print-vars 2021-12-04 20:09:04 +01:00
system system: support br2-external init systems 2020-10-14 22:48:42 +02:00
toolchain package/toolchain: rename GLIBC_COPY_NSSWITCH_FILE 2021-11-25 20:53:43 +01:00
utils utils/genrandconfig: reduce the maximum "size" of random configurations 2021-11-14 13:50:50 +01:00
.defconfig
.flake8 Revert ".flake8: fix check for 80/132 columns" 2021-01-02 17:38:20 +01:00
.gitignore
.gitlab-ci.yml .gitlab-ci.yml: use the Docker image from gitlab registry 2021-10-24 16:12:43 +02:00
CHANGES Update for 2021.11-rc3 2021-11-30 18:13:36 +01:00
Config.in Config.in: disable Fortify Source for microblaze 2021-08-23 23:08:05 +02:00
Config.in.legacy package/mpd: drop tidal option 2021-11-09 23:04:45 +01:00
COPYING
DEVELOPERS DEVELOPERS: add Joachim Wiberg as maintainer for inadyn 2021-12-04 23:12:21 +01:00
Makefile Makefile: really comment syntax colouring 2021-12-04 20:09:09 +01:00
Makefile.legacy
README docs: move the IRC channel away from Freenode 2021-05-29 22:16:23 +02:00

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on OFTC IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches