Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: c compiler cannot create executables (do_configure, gettext-native-0.17-r3)
Date: Sun, 08 Feb 2009 09:48:52 +0100	[thread overview]
Message-ID: <gmm69k$act$1@ger.gmane.org> (raw)
In-Reply-To: <3ea34a000902071827x6e28e053m837c6334ca5939f@mail.gmail.com>

On 08-02-09 03:27, Christopher Friedt wrote:
> Hi Koen
>
> I determined what the problem was - ccache - I think that because
> ccache existed on my (well, my work's) build machine, that it
> consistently interfered with *-native.
>
> The remote machine I'm building OE on is a CentOS 4.5 box (not my
> preference, but the IT manager's), and my solution was to just remove
> ccache entirely.

CCACHE="" in local.conf. It seems that Red Hat based OS'es don't have a 
ccache that plays nice :(

regards,

Koen




      reply	other threads:[~2009-02-08  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07 16:25 c compiler cannot create executables (do_configure, gettext-native-0.17-r3) Christopher Friedt
2009-02-07 16:47 ` Koen Kooi
2009-02-08  2:27   ` Christopher Friedt
2009-02-08  8:48     ` Koen Kooi [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='gmm69k$act$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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