Files
meta-openembedded/meta-oe
Khem Raj 10039570ec kernel-module-emlog: Use compile task from module bbclass
This ensures that right CC/LD is used when building the module, which
should be KERNEL_CC and KERNEL_LD, otherwise it starts to use DISTRO
default ld and cc which could be non-gcc and non-bfd liker which is must
for building kernel and modules

Also hides a gold linker failure seen on aarch64

| aarch64-yoe-linux-musl-ld: internal error in set_address, at ../../gold/output.h:322

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Fabio Berton <fabio.berton@ossystems.com.br>
2019-12-01 11:24:26 -08:00
..
2019-11-24 07:18:11 -08:00
2019-11-27 20:07:43 -08:00
2019-11-22 09:22:56 -08:00
2019-11-29 16:41:22 -08:00

meta-oe
=======

This layer depends on:

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

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

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/openembedded-core
to share your patches, this is preferred for patch sets consisting of more than one patch.

Other services like gitorious, 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>