buildroot/package/efibootmgr, branch 2017.08.1

package/e*: fix wrapping of Config.in help text

2017-07-31T17:08:47+00:00

The check-package script when ran gives warnings on text wrapping on all of these Config files. This patch cleans up all warnings related to the text wrapping for the Config files starting with the letter e in the package directory. The appropriate indentation is: <2 spaces><62 chars> See http://nightly.buildroot.org/#writing-rules-config-in for more information. Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

efibootmgr: fix build with gcc 7.x

2017-07-22T21:19:53+00:00

Now that the build of efivar with gcc 7.x has been fixed by commit 0ca30170345a81f5f21e4ef4424b1f186cde1988 ("efivar: fix build with gcc 7"), efibootmgr fails similarly with gcc 7.x. This commit backports an upstream patch that fixes this issue. Signed-off-by: Thomas Petazzoni

efibootmgr: use the new gettext logic

2017-07-04T23:27:25+00:00

This commit switches to use the new gettext logic, which involves: - using TARGET_NLS_DEPENDENCIES instead of hand-encoded dependencies on gettext/host-gettext - using TARGET_NLS_LIBS to force linking against libintl - dropping BR2_PACKAGE_GETTEXT selection The BR2_USE_WCHAR dependency was needed for gettext, now that we no longer need gettext, we can also get rid of this dependency. Signed-off-by: Thomas Petazzoni

efibootmgr: don't download patch from Github

2017-07-02T22:05:18+00:00

Patches downloaded from Github are not stable, so bring them in the tree. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

efibootmgr: backport upstream patch to fix build with gcc 6.x

2017-05-11T07:46:40+00:00

efibootmgr was built with -fshort-wchar, which causes gcc to use 2-byte wchar_t instead of the normal 4-byte wchar_t. But this doesn't work anymore with gcc 6.x, as it causes a build failure: /home/test/autobuild/run/instance-3/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-gnueabihf/6.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld: warning: efibootmgr.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail /home/test/autobuild/run/instance-3/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-gnueabihf/6.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld: warning: efi.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail /home/test/autobuild/run/instance-3/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-gnueabihf/6.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld: warning: unparse_path.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail Upstream solution was do simply drop -fshort-wchar: https://github.com/rhinstaller/efibootmgr/commit/3466fd05c8c6f1052e0426d64eed40f8a88fd78f So this commit simply backports this upstream patch. Fixes: http://autobuild.buildroot.net/results/87c3ff2427331eb9ab31c9eb685fe80954a0a98f/ Signed-off-by: Thomas Petazzoni

package makefiles: clean up backslash spacing.

2017-04-22T13:57:23+00:00

The check-package script when ran gave warnings on only using one space before backslashes on all of these makefiles. This patch cleans up all warnings related to the one space before backslashes rule in the make files in the package directory. Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

boot, linux, package: use SPDX short identifier for GPLv2/GPLv2+

2017-04-01T13:16:38+00:00

We want to use SPDX identifier for license strings as much as possible. SPDX short identifier for GPLv2/GPLv2+ is GPL-2.0/GPL-2.0+. This change is done by using following command. find . -name "*.mk" | xargs sed -ri '/LICENSE( )?[\+:]?=/s/\/GPL-2.0/g' Signed-off-by: Rahul Bedarkar Signed-off-by: Thomas Petazzoni

efibootmgr: depends on wchar

2016-12-07T22:45:35+00:00

After commit 3ae07b4746 recently, efibootmgr now selects BR2_PACKAGE_GETTEXT if the toolchain requires it. gettext depends on wchar, so this dependency should be propagated as well. menuconfig currently complains loudly if you select efibootmgr, with an error such as: warning: (... && BR2_PACKAGE_EFIBOOTMGR ... && ) selects BR2_PACKAGE_GETTEXT which has unmet direct dependencies (BR2_USE_WCHAR) Signed-off-by: Erico Nunes Signed-off-by: Thomas Petazzoni

efivar: introduce BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS

2016-12-07T22:41:52+00:00

efivar only makes sense on platforms that support UEFI. UEFI is only supported by some architectures at the moment, being mostly employed on platforms such as x86, x86_64 and aarch64. Some other platforms such as MIPS and PowerPC may have some unofficial UEFI support. UEFI is also limited to little endian architectures. efivar was being supported in Buildroot without architecture restrictions so far, however this has led to the creation of a number of hacks in the recipes, mostly for architectures that are not supported by UEFI. In order to avoid spending more time to debug these failures and maintaining more hacks for unsupported architectures, efivar can be restricted to that platforms where it makes sense and where it is more likely to receive some testing and actual usage. The existing hacks for the now unsupported architectures are removed, and the dependency is propagated to efibootmgr as it depends on efivar. Signed-off-by: Erico Nunes Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

efivar: not available for static builds

2016-12-05T20:31:08+00:00

efivar uses dlfcn.h which is not available in static builds configuration. Also propagate dependency to efibootmgr. This commit also does s/requires/needs/ in comment while at it. Fixes: http://autobuild.buildroot.net/results/ab3/ab32ccacfac2e65e1fcb307058d06c3d0122979d/ Signed-off-by: Rahul Bedarkar Signed-off-by: Thomas Petazzoni