Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [dylan, master][PATCH] autotools.bbclass: Fix race with sed-native
Date: Tue, 08 Oct 2013 15:03:32 +0200	[thread overview]
Message-ID: <lytxgrvrrv.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1381234763.29912.39.camel@ted> (Richard Purdie's message of "Tue, 08 Oct 2013 13:19:23 +0100")

Richard Purdie
<richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
writes:

> The list of things we assume are ok is relatively small and we look at
> new issues on a case by case basis. I think sed is well enough
> established and well enough behaved to be something we can rely on. In
> general we don't rely on much. Do you have any other specific things you
> worry about? 

ccache... it causes big problems when CC='ccache real-gcc' is set and
ccache-native gets rebuilt in parallel.  A customer had problems when
building apr-utils (libtool reported missing '--tag=cc' option) which
are very likely related to a no-ccache -> ccache-available situation.

It is very difficult to recover from such things because CCACHE is in
BB_HASHBASE_WHITELIST.



Enrico


  reply	other threads:[~2013-10-08 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 23:35 [dylan, master][PATCH] autotools.bbclass: Fix race with sed-native Richard Tollerton
2013-10-05  3:22 ` Saul Wold
2013-10-05  7:37   ` Richard Purdie
2013-10-08  2:44     ` Richard Tollerton
2013-10-08 12:19       ` Richard Purdie
2013-10-08 13:03         ` Enrico Scholz [this message]
2013-10-08 17:47         ` Richard Tollerton
2013-10-10  9:00           ` Richard Purdie
2013-10-10 10:29             ` Phil Blundell
2013-10-08  2:55   ` Richard Tollerton

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=lytxgrvrrv.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox