From: Martin Jansa <martin.jansa@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: u-boot do_compile should be reentrant even with ld-is-gold
Date: Wed, 1 Aug 2012 13:59:43 +0200 [thread overview]
Message-ID: <20120801115943.GC16306@jama.jama.net> (raw)
In-Reply-To: <CAP9ODKoa2AWz=A8YOmcBDXjDt9jDXaUsgo1WOVrMsivwU--m_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Wed, Aug 01, 2012 at 08:48:08AM -0300, Otavio Salvador wrote:
> On Wed, Aug 1, 2012 at 3:50 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > reexecuting do_compile in u-boot causes .bfd being appended multiple
> > times and resulting in errors like:
> > /bin/bash: arm-oe-linux-gnueabi-ld.bfd.bfd.bfd: command not found
>
> I am just wondering why it'd end re-executed? due changes on sstate hash?
e.g. when it fails due to compile error and someone reexecutes it then
he will see arm-oe-linux-gnueabi-ld.bfd.bfd.bfd instead of real compile
error.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-08-01 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 6:50 u-boot do_compile should be reentrant even with ld-is-gold Martin Jansa
2012-08-01 6:54 ` Martin Jansa
2012-08-01 23:02 ` Khem Raj
2012-08-02 11:50 ` Martin Jansa
2012-08-02 12:09 ` [PATCH] u-boot.inc: fix regexp used when ld-is-gold Martin Jansa
2012-08-02 14:32 ` Khem Raj
2012-08-02 14:37 ` Martin Jansa
2012-08-02 14:42 ` Otavio Salvador
2012-08-02 14:30 ` u-boot do_compile should be reentrant even with ld-is-gold Khem Raj
2012-08-02 14:37 ` Martin Jansa
2012-08-02 14:38 ` Otavio Salvador
2012-08-01 11:48 ` Otavio Salvador
2012-08-01 11:59 ` Martin Jansa [this message]
2012-08-01 12:32 ` Otavio Salvador
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=20120801115943.GC16306@jama.jama.net \
--to=martin.jansa@gmail.com \
--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