Files
meta-openembedded/meta-oe
Wang Mingyu c840260ff4 minicoredumper: upgrade 2.0.2 -> 2.0.3
0001-minicoredumper_demo-Use-optnone-attribute-with-clang.patch
removed since it's included in 2.0.3

Changelog:
==========
* Dump zero-blocks as 4KB blocks instead of single bytes to speed up
   piping to the compressor. (Only relevant if tar is not used.)

 * Drop core data exceeding the ustar 8GB limit. The core file is
   appropriately truncated and the actions are logged. This fixes tar
   file corruption for core files >8GB.

 * Known problems:

     - If tar is active, core files larger than 8GB will be
       truncated. If it is known that the core files will be >8GB and
       the full core file is needed, tar must be disabled.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2023-02-18 13:19:36 -08:00
..
2023-02-15 08:23:49 -08:00
2023-02-15 08:23:49 -08:00
2023-01-17 01:05:52 -08:00

meta-oe
=======

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit
e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
packages to fullfit this might have different names on different host distributions
e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu
sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
to share your patches, this is preferred for patch sets consisting of more than one patch.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well,
'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy
to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj <raj.khem@gmail.com>