Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Due to default -mfloat-abi=softfp facing below error log: "Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)" Ref:

This sample program does not exist anymore. Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- .../zephyr-getchar/zephyr-getchar_git.bb | 26 ------------------- 1 file changed, 26

Dropped the patches which are not required anymore. Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- .../newlib/gettimeofday-header-fix.patch | 20 -

Hi I am a newbie in yocto can anyone help me in finding the md5sum of the file before downloading the file in yocto.

Howdy! Have fun, and feel free to return with arising questions :) Anything that works for you is a decent usecase. In terms of Yocto/OE, the line between decent and non-decent is less a technical

thanks for stepping up. I think this is a good idea. Bringing tools closer to developers and having the ability to run it offline, perhaps before submitting patches is going to improve the

Thanks! It sounds like I am not stepping into an historical tarpit then. There are so many references to patchutils in the Yocto ecosystem that I figured there just had to be some reason for the

Thanks for the reminder. Final note, Back in the days, uClibc had a compile time option to select one behaviour or the other. Cheers, A.

Sorry, I was too quick replying here... It's simply defaulting to no because of cross-compilation, no matter what libc is in use. I wanted to be conservative, but Adrian reminded me of actual

From: Andre' Draszik <git@...> diffutils' version of autoconf tries to run a test program to determine if malloc() and realloc() behave like in glibc, i.e. returning non-NULL when given 0

Howdy! Write a recipe and submit :) I don't think there was ever a "conscious decision" to not support a specific package for non-technical reasons. And this one doesn't also look like it has any

Hi, I checked the layer index (and google) and I find no references to a bitbake recipe for patchutils. Was there a conscious decision to not maintain a recipe for patchutils? Or is this something

The jm_cv_func_working_malloc test is: main () { exit (malloc (0) ? 0 : 1); } The C standard says that this is implementation defined, both results are permitted. glibc has the

That's musl specific, because it's a property of the C-library in use. E.g. somebody could be using this with an outdated vendor(?) toolchain using an old glibc which could behave

Why is this musl-specific? Does the configure explicitly detect glibc and know it's good, or should we do this for glibc too? Ross

diffutils tries to run a test program to determine if malloc() and realloc() work, i.e. whether they fail if given 0 for size. running a test program doesn't work when cross-compiling, so it defaults

Paul, Thanks for stepping up as the Maintainer. - Armin On 1/8/20 4:48 AM, Paul Barker wrote:

Suggestions made sound like major enhancements to me. My favourites are: extend to other layers and local operation :) Thanks for taking care Andreas

See included patch. Signed-off-by: André Draszik <git@...> --- ...ilation-with-64bit-time_t-on-32bit-a.patch | 46 +++++++++++++++++++ recipes-extended/diffutils/diffutils_2.8.1.bb | 1 + 2