mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-01-04 16:10:10 +00:00
fa91738a94
Remove -m32 from CFLAGS even for -cross recipe. Also remove
${GDB_CONF_FLAGS} from GDB_TARGET variable (that is passed to the gdb
configuration) since the use of GDB_CONF_FLAGS is removed by
0001-cross_add_configure_option.patch.
Signed-off-by: Goran Cengic <cengic@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers/meta-python | ||
| lib/oeqa/selftest/cases | ||
| licenses | ||
| recipes-benchmark | ||
| recipes-bsp | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-crypto | ||
| recipes-dbs | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-kernel | ||
| recipes-multimedia | ||
| recipes-navigation | ||
| recipes-printing | ||
| recipes-security | ||
| recipes-shells | ||
| recipes-support | ||
| recipes-test | ||
| COPYING.MIT | ||
| README | ||
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>