From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] angstrom-2008.1: bump uclibc to 0.9.30.3 which unbreaks x264
Date: Wed, 01 Dec 2010 12:07:40 +0000 [thread overview]
Message-ID: <4CF63A8C.1040502@xora.org.uk> (raw)
In-Reply-To: <20101201115806.GQ10755@ibawizard.net>
On 01/12/2010 11:58, Petr Štetiar wrote:
> Bernhard Guillon <Bernhard.Guillon@opensimpad.org> [2010-12-01 12:41:31]:
>
>> This is true. We could add some python foo and check for angstrom? In my
>> opinion the log2f patch is of no real harm. The tls support might be a
>> problem.
> Why to not move to some newer version of uClibc directly, without that patch
> at all?
>
because Angstrom 2008.1 is an already released distro. We don't like
switching toolchains at last minute.
Graeme
next prev parent reply other threads:[~2010-12-01 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 10:47 [PATCH] angstrom-2008.1: bump uclibc to 0.9.30.3 which unbreaks x264 Petr Štetiar
2010-11-26 10:53 ` Andrea Adami
2010-11-26 11:00 ` Petr Štetiar
2010-11-26 11:20 ` Koen Kooi
2010-11-26 18:37 ` Andrea Adami
2010-11-27 14:02 ` Petr Štetiar
2010-11-27 14:13 ` Andrea Adami
2010-11-27 14:27 ` Andrea Adami
2010-12-01 11:41 ` Bernhard Guillon
2010-12-01 11:58 ` Petr Štetiar
2010-12-01 12:07 ` Graeme Gregory [this message]
2010-12-01 12:35 ` Andrea Adami
2010-12-01 13:19 ` Frans Meulenbroeks
2010-12-01 12:08 ` Andrea Adami
2010-11-26 23:22 ` [PATCH] x264-r2245: add a hack for uclibc - replace log2f(x) with logf(x)/logf(2) Bernhard.Guillon
2011-01-04 13:32 ` Graeme Gregory
2010-11-26 23:29 ` [PATCH] angstrom-2008.1: bump uclibc to 0.9.30.3 which unbreaks x264 Bernhard Guillon
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=4CF63A8C.1040502@xora.org.uk \
--to=dp@xora.org.uk \
--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.