[OE-core] [PATCH 0/1][master] Fix for Bug 5403
This fixes a problem seen when accessing function params in systemtap on certain platforms, due to flaky debuginfo. Tested on the following machines with various systemtap scripts: qemuppc qemuarm qemux86 qemux86-64 crownbay nuc The following changes since commit 005af45191ded6185c618c708181b31281e43092: bitbake: fetch2: avoid printing "no checksum" error message twice (2013-12-22 14:29:13 +) are available in the git repository at: git://git.yoctoproject.org/poky-contrib.git tzanussi/systemtap-bug-5403-master http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/systemtap-bug-5403-master Tom Zanussi (1): systemtap: Add --enable-prologues to configuration meta/recipes-kernel/systemtap/systemtap_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 1.8.3.1 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] systemtap: Add --enable-prologues to configuration
In some cases, the debuginfo generated by the compiler is insufficient
for systemtap to figure out function param locations; using -P allows
it to use prologue searching to find the correct locations.
Enable prologue searching in the configuration so the user doesn't
have to specify it manually.
Fixes [YOCTO #5403].
Signed-off-by: Tom Zanussi
---
meta/recipes-kernel/systemtap/systemtap_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/systemtap/systemtap_git.bb
b/meta/recipes-kernel/systemtap/systemtap_git.bb
index bcc826a..3fd27bc 100644
--- a/meta/recipes-kernel/systemtap/systemtap_git.bb
+++ b/meta/recipes-kernel/systemtap/systemtap_git.bb
@@ -12,7 +12,7 @@ RDEPENDS_${PN}_class-nativesdk += "python-native"
EXTRA_OECONF += "--with-libelf=${STAGING_DIR_TARGET} --without-rpm \
--without-nss --without-avahi --without-dyninst \
---disable-server --disable-grapher \
+--disable-server --disable-grapher --enable-prologues \
ac_cv_prog_have_javac=no \
ac_cv_prog_have_jar=no "
--
1.8.3.1
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1][dora] - Fix for Bug 5403
On 12/30/2013 09:54 PM, Tom Zanussi wrote: Hi Robert, Yes, I'm still testing the one for master - will post tomorrow. Right, we should have the master patch backported into dora hopefully the changes will be the same. Sau! Tom On Tue, 2013-12-31 at 09:29 +0800, Robert Yang wrote: Hi Tom, Thanks, do we also need a patch for master ? // Robert On 12/31/2013 01:31 AM, Tom Zanussi wrote: This fixes a problem seen when accessing function params in systemtap on certain platforms, due to flaky debuginfo. Tested on the following machines with various systemtap scripts: qemuppc qemuarm qemux86 qemux86-64 crownbay nuc The following changes since commit 3cf2d232529c4fd6b58f87ddbf3df9d805e4180f: libsoup-2.4: add intltool-native to DEPENDS (2013-12-20 09:29:05 +) are available in the git repository at: git://git.yoctoproject.org/poky-contrib.git tzanussi/systemtap-bug-5403-dora http://git.yoctoproject.org/cgit.cgi//log/?h=tzanussi/systemtap-bug-5403-dora Tom Zanussi (1): systemtap: Add --enable-prologues to configuration meta/recipes-kernel/systemtap/systemtap_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] lib/oe/patch.py: Prefer "git am" over "git apply" when applying git patches
Ping?
Alternatively, the system could also have an option for further
fine-tuning what to do with git patches
On Tue, Dec 24, 2013 at 12:44 PM, Laszlo Papp wrote:
> It is better to use "git am" when possible to preserve the commit messages and
> the mail format in general for patches when those are present. A typical use
> case is when developers would like to keep the changes on top of the latest
> upstream, and they may occasionally need to rebase. This is not possible with
> "git diff" and "diff" generated patches.
>
> Since this is not always the case, the fallback would be the "git apply"
> operation which is currently available.
>
> Signed-off-by: Laszlo Papp
> ---
> meta/lib/oe/patch.py | 20 +---
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/meta/lib/oe/patch.py b/meta/lib/oe/patch.py
> index 59abd0a..b085c9d 100644
> --- a/meta/lib/oe/patch.py
> +++ b/meta/lib/oe/patch.py
> @@ -203,17 +203,23 @@ class GitApplyTree(PatchTree):
> PatchTree.__init__(self, dir, d)
>
> def _applypatch(self, patch, force = False, reverse = False, run = True):
> -shellcmd = ["git", "--git-dir=.", "apply", "-p%s" %
> patch['strippath']]
> +def _applypatchhelper(shellcmd, patch, force = False, reverse =
> False, run = True):
> +if reverse:
> +shellcmd.append('-R')
>
> -if reverse:
> -shellcmd.append('-R')
> +shellcmd.append(patch['file'])
>
> -shellcmd.append(patch['file'])
> +if not run:
> +return "sh" + "-c" + " ".join(shellcmd)
>
> -if not run:
> -return "sh" + "-c" + " ".join(shellcmd)
> +return runcmd(["sh", "-c", " ".join(shellcmd)], self.dir)
>
> -return runcmd(["sh", "-c", " ".join(shellcmd)], self.dir)
> +try:
> +shellcmd = ["git", "--work-tree=.", "am", "-3", "-p%s" %
> patch['strippath']]
> +return _applypatchhelper(shellcmd, patch, force, reverse, run)
> +except CmdError:
> +shellcmd = ["git", "--git-dir=.", "apply", "-p%s" %
> patch['strippath']]
> +return _applypatchhelper(shellcmd, patch, force, reverse, run)
>
>
> class QuiltTree(PatchSet):
> --
> 1.8.5.1
>
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] Adding irssi 0.8.16-rc1 recipe
Op 27 dec. 2013, om 18:30 heeft krzysztof.m.syw...@intel.com het volgende geschreven: > From: Krzysztof Sywula > > --- > meta/recipes-connectivity/irssi/irssi_0.8.16-rc1.bb | 11 +++ that should be 0.8.15+0.8.16-rc1 to conform to the versioning policy ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Why do we allow empty -dev/-dbg packages ?
On Tue, Dec 31, 2013 at 09:49:21AM +0800, ChenQi wrote:
> Hi All,
>
> This might be a dummy question, but it has been puzzling me for some
> time. So if someone could give me some explanation, that would be really
> appreciated.
>
> In bitbake.conf, we have:
> ALLOW_EMPTY_${PN}-dev = "1"
> ALLOW_EMPTY_${PN}-dbg = "1"
>
> That means we allow emtpy -dev/-dbg packages. But what are the benefits
> of these empty -dev/-dbg packages?
In some cases it's useful to satisfy default dependcencies:
bitbake.conf:RDEPENDS_${PN}-staticdev = "${PN}-dev (= ${EXTENDPKGV})"
and -dev needs ${PN} even when it's empty in some recipes where all
files are split into separate packages
bitbake.conf:RDEPENDS_${PN}-dev = "${PN} (= ${EXTENDPKGV})"
Not sure about -dbg one.
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
