From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How to enforce ${B} = ${S} builds globally?
Date: Tue, 23 Dec 2014 11:58:12 +0100 [thread overview]
Message-ID: <ly8uhyab0b.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1419322751.1777.3.camel@linuxfoundation.org> (Richard Purdie's message of "Tue, 23 Dec 2014 08:19:11 +0000")
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>> | test:
>> | /srv/oe/cache/bld/f95aceac-8952-bd61-430a-dfcdf48db33c/work/cortexa9t2hf-vfp-neon-linux-gnueabi/test/1.0-r0/test-1.0/test.c:2:
>> | main: Assertion `0' failed.
>>
>> instead of
>>
>> | test: test.c:2: main: Assertion `0' failed.
>
>
> Lets say you just shared this error as a cut and paste to me asking for
> help. In the latter case, I have no idea what happened. In the former, I
> can tell you were building for an arm system, your recipe PN was test
> and so on.
Version numbers can be extracted more detailed from package management
data (e.g. in case of kernel, you do not see the git revision in the
BUG() but it is shown in 'opkg info kernel\*').
fwiw, I wrote the posting as an end-user who had to deal with 'GST_DEBUG=9
gst-launch' output where 70% of the line is filled with a redundant and
uninteresting path.
Enrico
prev parent reply other threads:[~2014-12-23 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 11:24 How to enforce ${B} = ${S} builds globally? Enrico Scholz
2014-12-23 8:19 ` Richard Purdie
2014-12-23 10:58 ` Enrico Scholz [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=ly8uhyab0b.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox