From: Robert Yang <liezhi.yang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] btrfs-tools: workaround DEBUG_BUILD for arm
Date: Wed, 11 Mar 2015 10:50:39 +0800 [thread overview]
Message-ID: <54FFAD7F.3070706@windriver.com> (raw)
In-Reply-To: <CAMKF1sq2BnBr_cdVJOngc5Ltmsiv2pzd7aFQFpE8cn7WgVtWwA@mail.gmail.com>
On 03/11/2015 10:12 AM, Khem Raj wrote:
> On Tue, Mar 10, 2015 at 7:05 PM, Robert Yang <liezhi.yang@windriver.com> wrote:
>> [CC] btrfs-show-super.o
>> {standard input}: Assembler messages:
>> {standard input}:3368: Error: invalid operands (.text and *UND* sections)
>> for `-'
>> {standard input}:3374: Error: invalid operands (.text and *UND* sections)
>> for `-'
>> [AR] libbtrfs.a
>
> I meant detailed. use V=1
Thanks, here it is:
| [CC] cmds-fi-disk_usage.o
| arm-poky-linux-gnueabi-gcc -march=armv5e -marm -mthumb-interwork
--sysroot=/buildarea/lyang1/test_w5/tmp/sysroots/qemuarm -Wall
-D_FILE_OFFSET_BITS=64 -DBTRFS_FLAT_INCLUDES -D_XOPEN_SOURCE=700 -D_GNU_SOURCE
-fno-strict-aliasing -fPIC -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -O
-fno-omit-frame-pointer -g -feliminate-unused-debug-types -pipe -c
cmds-fi-disk_usage.c
| {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
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
// Robert
>
>
prev parent reply other threads:[~2015-03-11 2:50 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
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 [this message]
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=54FFAD7F.3070706@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.