The -flto change already disappeared in an earlier update.
-std=gnu11 and -Wmaybe-uninitialized are supported by gcc >= 4.7,
which covers all host distributions that are still supported.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
atexit is not a drop-in replacement for on_exit,
mark as incompatible with musl instead of adding
a broken patch.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The program sensors-detect in lmsensors can't read the cpu
information on ppc and arm arch, such as: fsl-t4xxx based on ppc.
This is because the program sensors-detect design for the x86 and
x86-64, but weak on ppc and arm.
So add the support for the ppc and arm, just add the correspond
field to read in sensors-detect.
Signed-off-by: Dengke Du <dengke.du@windriver.com>
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The library to modify EFI variables is useless without access to efivarfs, so
recommend the kernel package that has contains this module.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Since upstream efivar-37 pulibc efi_set_verbose in its
headers [daf3b6c Move verbosity headers to be public],
it is not necessary to delcare in efibootmgr.
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Multiple -dbg packages per recipe is not encouraged, and only one is
recommended and the code only works properly in some cases for one.
Add RPROVIDES_${PN}-dbg to be compatiable with previous dbg packages
requiring.
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Modern hardware doesn't really use PCMCIA so the support has been moved out of
oe-core. Move into meta-oe for people who still want it.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
fixes
WARNING: efivar-0.31-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to
incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch allow-multi-definitions-for-native.patch
patching file Make.rules
Hunk #1 succeeded at 20 with fuzz 2.
Now at patch allow-multi-definitions-for-native.patch
Now at patch 0003-efivar-fix-for-cross-compile.patch
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
