All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] btrfs-tools: workaround DEBUG_BUILD for arm
Date: Tue, 10 Mar 2015 10:32:21 +0000	[thread overview]
Message-ID: <1425983541.9701.50.camel@linuxfoundation.org> (raw)
In-Reply-To: <30f590c7e3d62ff1adb5d6b14fe0dca71f555f5f.1425979509.git.liezhi.yang@windriver.com>

On Tue, 2015-03-10 at 02:25 -0700, Robert Yang wrote:
> Workaround when:
> MACHINE = "qemuarm"
> DEBUG_BUILD = "1"
> 
> Errors:
> {standard input}: Assembler messages:
> {standard input}:3383: Error: invalid operands (.text and *UND* sections) for `-'
> {standard input}:3389: Error: invalid operands (.text and *UND* sections) for `-'
> make: *** [cmds-fi-disk_usage.o] Error 1
> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
>  .../btrfs-tools/btrfs-tools_git.bb                 |    7 +++++++
>  1 file changed, 7 insertions(+)

I really don't like workarounds like this. They tend to get left in the
recipes for ever more and never get fixed properly. Please just use
something like

DEBUG_BUILD_pn-btrfs-tools = "0"

or similar.

Cheers,

Richard



  reply	other threads:[~2015-03-10 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10  9:25 [PATCH 0/1] btrfs-tools: workaround DEBUG_BUILD for arm Robert Yang
2015-03-10  9:25 ` [PATCH 1/1] " Robert Yang
2015-03-10 10:32   ` Richard Purdie [this message]
2015-03-10 16:28   ` Khem Raj
2015-03-11  2:05     ` Robert Yang
2015-03-11  2:12       ` Khem Raj
2015-03-11  2:50         ` Robert Yang

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=1425983541.9701.50.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.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.