From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: Kill CCACHE. Implicit, automatic use of things which can fail is bad.
Date: Thu, 20 Aug 2009 03:43:57 -0400 [thread overview]
Message-ID: <20090820074357.GC459@denix.org> (raw)
In-Reply-To: <6ec4247d0908200032s44cd3230s9b3e0d06777116c3@mail.gmail.com>
On Thu, Aug 20, 2009 at 05:02:31PM +0930, Graham Gower wrote:
> 2009/8/20 Holger Hans Peter Freyther <holger+oe@freyther.de>:
> > On Thursday 20 August 2009 05:24:37 Chris Larson wrote:
> >> To re-enable, set CCACHE = "ccache ".
> >>
> >> Signed-off-by: Chris Larson <clarson@mvista.com>
> >
> > Could you elaborate on the need of that? Which platforms do you deal with that
> > break due the usage of ccache?
>
> I run Slackware 12.2, whose build of ccache does not seem to be
> accepted. I don't recall the exact mechanism of failure, but
> shasum-native fails before getting to any other pacakges. Currently I
> have to move the ccache binary out of my $PATH or OE tries to use it.
Same exact problem has been reported many times with RedHat-based distros as
well - it just fails to build shasum-native (the very first package) w/o any
meaningful messages...
--
Denys
next prev parent reply other threads:[~2009-08-20 8:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 3:24 [PATCH] cross.bbclass: keep TARGET_SYS & TARGET_PREFIX independent Chris Larson
2009-08-20 3:24 ` [PATCH] patch.bbclass: catch exceptions raised in the Resolve() Chris Larson
2009-08-20 3:24 ` [PATCH] patch.bbclass: Add "git" patchtool mechanism, which uses git-apply Chris Larson
2009-08-20 3:24 ` [PATCH] kernel.bbclass: Set EXTRA_OEMAKE to null for kernel Chris Larson
2009-08-20 3:24 ` [PATCH] kernel.bbclass: Install & package symvers as /boot/Module.symvers-<ver> Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: Kill CCACHE. Implicit, automatic use of things which can fail is bad Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: Add export for cross NM Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: BUILD_LDFLAGS: use $ORIGIN in the -rpath rather than a full path Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: only pass --no-check-certificate if wget supports it Chris Larson
2009-08-20 4:18 ` [PATCH] bitbake.conf: BUILD_LDFLAGS: use $ORIGIN in the -rpath rather than a full path Denys Dmytriyenko
2009-08-20 4:53 ` Chris Larson
2009-08-20 5:06 ` Denys Dmytriyenko
2009-08-20 5:49 ` [PATCH] bitbake.conf: Add export for cross NM Holger Hans Peter Freyther
2009-08-20 4:06 ` [PATCH] bitbake.conf: Kill CCACHE. Implicit, automatic use of things which can fail is bad Denys Dmytriyenko
2009-08-20 5:49 ` Holger Hans Peter Freyther
2009-08-20 7:32 ` Graham Gower
2009-08-20 7:43 ` Denys Dmytriyenko [this message]
2009-08-20 12:09 ` Martyn Welch
2009-08-20 12:05 ` [PATCH] kernel.bbclass: Install & package symvers as /boot/Module.symvers-<ver> Michael Smith
2009-08-20 3:43 ` [PATCH] kernel.bbclass: Set EXTRA_OEMAKE to null for kernel Denys Dmytriyenko
2009-08-20 3:55 ` [PATCH] patch.bbclass: Add "git" patchtool mechanism, which uses git-apply Denys Dmytriyenko
2009-08-20 12:04 ` [PATCH] cross.bbclass: keep TARGET_SYS & TARGET_PREFIX independent Michael Smith
2009-08-20 15:21 ` Chris Larson
2009-08-20 16:11 ` Michael Smith
2010-02-25 18:28 ` Tom Rini
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=20090820074357.GC459@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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.