agent-proxy is a simple, small proxy which is intended
for use with kgdb, or gdbserver type connections where
you want to share a text console and a debug session.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
When build crash with mips:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mips-linux-nat.c:157:1: error: conflicting types for 'ps_get_thread_area'
ps_get_thread_area (const struct ps_prochandle *ph,
^~~~~~~~~~~~~~~~~~
In file included from gdb_proc_service.h:26:0,
from mips-linux-nat.c:32:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This problem have been fixed on intel and arm plantform, we can use the
similar approch to fix it on mips.
Signed-off-by: Dengke Du <dengke.du@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
1. Upgrade crash to fix build failure with glibc 2.25.
2. Add the "id" to HOSTTOOLS in meta-oe/layer.conf
Signed-off-by: Dengke Du <dengke.du@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Clarify licensing and switch to github for fetching
* Delete empty /var/run
Fixes
minicoredumper-2.0.0: minicoredumper: Files/directories were installed but not shipped in any package:
/run
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* based on discussion in pndeprecated thread:
https://patchwork.openembedded.org/patch/137573/
update the messages to warn possible users that the
recipe will be removed before the end of the next development
cycle (before Yocto 2.4 is released).
* updated with:
sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs`
* then noticed couple recipes being blacklisted only based on
DISTRO_FEATURES, so removed those:
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb
meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb
meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb
meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb
meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb
meta-oe/recipes-navigation/gypsy/gypsy.inc
meta-oe/recipes-navigation/navit/navit.inc
meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb
* if it isn't fixed by this date, it's fair game to be removed
whenever someone gets around to i
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Support 4.8 kernel
* Add a patch to fix vmcore compressing for ppc64
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This avoids a "QA Issue: No GNU_HASH in the elf binary:".
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* remove tabs which sneaked in since last cleanup
* meta-oe layers are using consistent indentation with 4 spaces, see
http://www.openembedded.org/wiki/Styleguide
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Add makedumpfile 1.6.0
* Create alias for target such as powerpc as powerpc32
* Remove hardcode CFLAGS
* Add CFLAGS_COMMON to instead of CFLAGS so can flexibly
customize CFLAGS and not hardcode the CFLAGS as previously
* Forcibly to link dynamic library as the poky build
system doesn't build static library by default
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
minicoredumper provides an alternate core dump facility for Linux
to allow minimal and customized crash dumps
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
base_contains() is a compatibility wrapper and may warn in the future, so
replace all instances with bb.utils.contains().
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This patch adds the cross package for the crash recipe. I've built and
tested crash-cross for ARM on x86_64 host only.
The way to pass GDB_CONF_FLAGS and --target to GDB build without
removing -m32 from CFLAGS is awkward but that is what I could come up
with, without changing the patch files included with the recipe or
breaking target and native builds. Anyone got any ideas on how to
better do this?
Thanks,
Goran
Signed-off-by: Goran Cengic <cengic@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Add crash-native package.
* append EXTRA_OEMAKE option to find ncurses library
* pass right install DESTDIR
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* some layers already have recipes for linux-backports
* don't know about anyone still using this and fails in default setups
| make -C /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemuarm/kernel-source M=/home/jenkins/oe/world/shr-core/tmp-glibc/work/qemuarm-oe-linux-gnueabi/compat-wireless-all/3.6.8-r1.0/compat-wireless-3.6.8-1 modules
| make[1]: Entering directory `/home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemuarm/kernel-source'
| make[2]: Entering directory `/home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemuarm/kernel-build-artifacts'
| /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemuarm-oe-linux-gnueabi/compat-wireless-all/3.6.8-r1.0/compat-wireless-3.6.8-1/config.mk:21: *** "ERROR: compat-wireless by default supports kernels >= 2.6.24, try enabling only one driver though". Stop.
| make[2]: *** [_module_/home/jenkins/oe/world/shr-core/tmp-glibc/work/qemuarm-oe-linux-gnueabi/compat-wireless-all/3.6.8-r1.0/compat-wireless-3.6.8-1] Error 2
| make[2]: Leaving directory `/home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemuarm/kernel-build-artifacts'
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Upgrade crash from 7.1.2 to 7.1.3.
Add gdb source tarball and don't fetch and extract it during do_compile.
And do some format tweaks.
Exclude mips64 from COMPATIBLE_HOST which is not supported. And update
ARCH setting for arm64, ppc64 and mips32.
Add patch to enable parallel make for gdb. And don't write crash.target
which causes rebuild fails.
Backport patches to fix compile failures.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* building ktap-module without elfutils fails with:
ktap-module/0.4-r0/git/Makefile:107: No libelf found, disables symbol resolving, please install elfutils-libelf-devel/libelf-dev
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* even if it makes sense in this case, don't give bad example for other people to
copy & paste to other recipes, kernel modules should be only recommended, so that
it still works fine if someone includes the module inside kernel image
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* set PV so that it shows git revision and also automatically rebuilds them
when SRCREV is changed
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* this .inc file wasn't working since oe-core commit:
commit 106dab2fd0321e6b4e77b40111e59a3a31d329d4
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Fri Dec 19 17:46:27 2014 +0000
Subject: kernel: Fix non linux-yocto builds
* Fixes following do_configure error
| NOTE: make oldconfig
| make: *** No rule to make target `oldconfig'. Stop.
| ERROR: oe_runmake failed
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* it's possible to exclude ktap-module dependency from siggen, but
then we would need to exclude virtual/kernel and that doesn't work
we would need to list all posisble providers as
ktap->linux-yocto
ktap->linux-foo
....
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Changes:
- rename SUMMARY with length > 80 to DESCRIPTION
- rename DESCRIPTION with length < 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line
Note: don't bump PR
Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
libelf (elfutils) is required for resolving symbols in DSO and for sdt (taken
from ktap docs). The earlier v0.4 recipe built ktap against libelf if it was
found, thus enable it per default.
FFI needs to be enabled for both userspace and kernel module. Currently, it is
only supported for x86_64 (enforced when building ktap-module).
Signed-off-by: Anders Darander <anders@chargestorm.se>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
When ktap made the release announcement, the tag v0.3 seems to have moved. Set the
correct SRCREV for the announced v0.3.
Signed-off-by: Anders Darander <anders@chargestorm.se>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Ktap is a new scripting dynamic tracing tool for Linux.
>From kernel v3.13 it'll live inside the kernel tree, but for earlier kernels,
this recipe will be usefull.
Signed-off-by: Anders Darander <anders@chargestorm.se>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
* use INC_PR
* fix RDEPENDS
* use normal PV
* move checksums from .inc to .bb
* upgrade, because old version fails to build with a lot of errors like this:
compat-wireless-3.5-rc5-1/include/linux/compat-3.5.h:102:8: error: redefinition of 'struct tc_fq_codel_xstats'
* 3.5.4-1, 3.6.8-1 can failed when kernel option is missing:
| compat-wireless-all/3.5.4-r1.0/compat-wireless-3.5.4-1/drivers/net/ethernet/broadcom/b44.c:2342:2:
error: implicit declaration of function 'ssb_pcihost_register' [-Werror=implicit-function-declaration]
| cc1: some warnings being treated as errors
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This recipe was based on the compat-wireless.inc recipe from openembedded-classic
at commit 53784a5e2622582ce5e2ffb91bbdb573503ed75e
The .inc is there in order to make it possible to have such recipes:
$ cat compat-wireless-ath_0.bb
include compat-wireless.inc
do_configure() {
cd ${S}
./scripts/driver-select ath
}
0001-ath5k-fix-compilation-without-CONFIG_PCI.patch will have to be submitted upstream
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* in my env I have 7 copies now
./meta-smartphone/meta-htc/recipes-kernel/linux/linux.inc
./meta-smartphone/meta-nokia/recipes-kernel/linux/linux.inc
./meta-smartphone/meta-openmoko/recipes-kernel/linux/linux.inc
./meta-smartphone/meta-samsung/recipes-kernel/linux/linux.inc
./meta-smartphone/meta-palm/recipes-kernel/linux/linux.inc
./meta-ti/recipes-kernel/linux/linux.inc
./meta-handheld/recipes-kernel/linux/linux.inc
meta-smartphone's are 100% identical, meta-handheld is slightly
different (ARM_KEEP_OABI can be set in recipe after require .inc) and
meta-ti seems like much older version of linux.inc
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* packaging split from meta-openembedded has been accepted in oe-core
* as per commit id 1f40a5486f703684c5d1d7360ef3cbdf75577495
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
