Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen.kooi@linaro.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] grub git: workaround debugedit problems for 64 bit targets
Date: Tue, 21 Jan 2014 10:40:33 +0100	[thread overview]
Message-ID: <52DE4091.8000104@linaro.org> (raw)
In-Reply-To: <CAP9ODKoLqJ63=wKJpbE3ezEN2QXO0We_yJcmdRL9qoCc0zp1+A@mail.gmail.com>

On 01/16/2014 11:47 AM, Otavio Salvador wrote:
> On Thu, Jan 16, 2014 at 8:46 AM, Koen Kooi <koen.kooi@linaro.org
> <mailto:koen.kooi@linaro.org>> wrote:
>
>     Op 16 jan. 2014, om 11:38 heeft Otavio Salvador
>     <otavio@ossystems.com.br <mailto:otavio@ossystems.com.br>> het
>     volgende geschreven:
>      > On Thu, Jan 16, 2014 at 7:27 AM, Koen Kooi <koen.kooi@linaro.org
>     <mailto:koen.kooi@linaro.org>> wrote:
>      > On 01/15/2014 12:22 PM, Otavio Salvador wrote:
>      > On Wed, Jan 15, 2014 at 8:15 AM, Koen Kooi <koen.kooi@linaro.org
>     <mailto:koen.kooi@linaro.org>
>      > <mailto:koen.kooi@linaro.org <mailto:koen.kooi@linaro.org>>> wrote:
>      >
>      >     I've limited it to 64bit targets, but to be honest debug
>     splitting
>      >     doesn't make sense for grub since it won't run in your rootfs and
>      >     attaching gdb is pretty much impossible.
>      >
>      >     Signed-off-by: Koen Kooi <koen.kooi@linaro.org
>     <mailto:koen.kooi@linaro.org>
>      >     <mailto:koen.kooi@linaro.org <mailto:koen.kooi@linaro.org>>>
>      >
>      >
>      >
>      > I'd prefer to remove the debug systems than skip the split. What
>     others
>      > think?
>      >
>      > I'm not sure what you mean by that, do you mean using
>     INHIBIT_PACKAGE_STRIP or something else?
>      >
>      >
>      > Yes and be sure it has been stripped during build.
>
>     That seems to be a lot more work for the same effect. Stripping
>     isn't the problem, it's debugedit trying to do its magic that fails.
>
>
> Well, if not stripped the symbols will be left in the binaries which is
> not expected.

I've looked into package.bbclass and it's a classic case of code not 
matching docs :(

-- 
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs


  reply	other threads:[~2014-01-21  9:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 10:15 [PATCH] grub git: workaround debugedit problems for 64 bit targets Koen Kooi
2014-01-15 11:22 ` Otavio Salvador
2014-01-16  9:27   ` Koen Kooi
2014-01-16 10:38     ` Otavio Salvador
2014-01-16 10:46       ` Koen Kooi
2014-01-16 10:47         ` Otavio Salvador
2014-01-21  9:40           ` Koen Kooi [this message]
2014-02-12  8:03 ` Koen Kooi
2014-02-12  8:31   ` Richard Purdie
2014-02-15 10:27     ` Koen Kooi
2014-03-13  9:08       ` Koen Kooi
2014-04-08 12:46         ` Koen Kooi
2014-04-12  8:59           ` Koen Kooi

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=52DE4091.8000104@linaro.org \
    --to=koen.kooi@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox