From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf, cross.bbclass: Make multi-machine toolchains to co-exist
Date: Fri, 30 Jul 2010 07:31:20 -0700 [thread overview]
Message-ID: <4C52E238.80603@mentor.com> (raw)
In-Reply-To: <i2u4cr$gkg$1@dough.gmane.org>
Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 30-07-10 09:42, Khem Raj wrote:
>> From: Tom Rini <tom_rini@mentor.com>
>>
>> the patch Tom sent has line breaks etc. this is same patch formatted for anybody to test
>
> MACHINE=beagleboard bitbake ffmpeg:
>
> | running configure fragment for nptl/sysdeps/pthread
> | configure: error: compiler support for __thread is required
> | ERROR: Function do_configure failed
> NOTE: package glibc-initial-2.9-r36.3: task do_configure: Failed
That's odd. My beagleboard build got to mesa before my laptop hd filled
up overnight. I'll try doing just beagle shortly
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-30 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 7:42 [PATCH] bitbake.conf, cross.bbclass: Make multi-machine toolchains to co-exist Khem Raj
2010-07-30 9:01 ` Koen Kooi
2010-07-30 14:31 ` Tom Rini [this message]
2010-07-30 15:42 ` Khem Raj
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=4C52E238.80603@mentor.com \
--to=tom_rini@mentor.com \
--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.