All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	 openembedded-core@lists.openembedded.org
Cc: Naveen Saini <naveen.kumar.saini@intel.com>
Subject: Re: [OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES
Date: Mon, 19 Apr 2021 21:42:55 +0100	[thread overview]
Message-ID: <6058118357d8a7604faaa961066937f346fcaa7c.camel@linuxfoundation.org> (raw)
In-Reply-To: <16774CB2FBD0E460.32333@lists.openembedded.org>

On Mon, 2021-04-19 at 16:41 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Mon, 2021-04-19 at 11:00 +0200, Alexander Kanavin wrote:
> > Obtaining debug information by having it served automatically via http
> > is far more pleasant than messing about with debugfs and gdbserver or
> > transferring and installing -dbg packages by hand.
> > 
> > I believe we should follow the desktop distros and have it enabled
> > out of the box. Please see the following commit for the description
> > of how it works.
> > 
> > Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> > ---
> >  meta/conf/distro/include/default-distrovars.inc  | 2 +-
> >  meta/recipes-devtools/binutils/binutils_2.36.bb  | 2 +-
> >  meta/recipes-devtools/elfutils/elfutils_0.183.bb | 2 +-
> >  meta/recipes-devtools/gdb/gdb-common.inc         | 2 +-
> >  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> I agree we should do this, it did blow up in testing:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/3289/steps/11/logs/stdio
> 
> Hopefully an easy fix?

Also:

https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/1993
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1705

(elfutils ptest warning)

Cheers,

Richard


  parent reply	other threads:[~2021-04-19 20:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  9:00 [PATCH 1/4] scripts/oe-debuginfod: correct several issues Alexander Kanavin
2021-04-19  9:00 ` [PATCH 2/4] libmicrohttpd: add a recipe from meta-oe Alexander Kanavin
2021-04-19 15:45   ` [OE-core] " Khem Raj
2021-04-20 12:07     ` Alexander Kanavin
2021-04-19  9:00 ` [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES Alexander Kanavin
2021-04-19 15:41   ` [OE-core] " Richard Purdie
     [not found]   ` <16774CB2FBD0E460.32333@lists.openembedded.org>
2021-04-19 20:42     ` Richard Purdie [this message]
2021-04-20 12:06       ` Alexander Kanavin
2021-04-19  9:00 ` [PATCH 4/4] dev-manual/common-tasks.rst: correct the documentation for debuginfod Alexander Kanavin
2021-04-19 10:11   ` [OE-core] " Richard Purdie
2021-04-19 10:33     ` [docs] " Quentin Schulz
2021-04-19 12:39       ` Alexander Kanavin
2021-04-19 12:52         ` Quentin Schulz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6058118357d8a7604faaa961066937f346fcaa7c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=naveen.kumar.saini@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.