From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fbdump: Make fbdump available only to x86/x86_64/arm architectures
Date: Wed, 14 Mar 2012 13:56:56 +0000 [thread overview]
Message-ID: <4F60A3A8.9000201@imgtec.com> (raw)
In-Reply-To: <20120314125527.5090807b@skate>
On 03/14/2012 11:55 AM, Thomas Petazzoni wrote:
> Le Wed, 14 Mar 2012 11:48:45 +0000,
> Markos Chandras <Markos.Chandras@imgtec.com> a ?crit :
>
>> Actually I don't think glibc supports ARM at all. From glibc's README file
>>
>> "The GNU C Library supports these configurations for using Linux kernels:
>>
>> i[34567]86-*-linux-gnu
>> x86_64-*-linux-gnu
>> powerpc-*-linux-gnu
>> powerpc64-*-linux-gnu
>> s390-*-linux-gnu
>> s390x-*-linux-gnu
>> ia64-*-linux-gnu
>> sparc*-*-linux-gnu
>> sparc64*-*-linux-gnu"
>
> It might be in glibc-ports, so that's why you don't see it in the main
> glibc README. But definitely, glibc runs on ARM, PowerPC. Millions of
> devices are using it as we are speaking :-)
>
> Thomas
Yeah I was talking for the official glibc git tree. I have no idea if
this function is supported in glibc-ports or not.
--
markos
next prev parent reply other threads:[~2012-03-14 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 10:02 [Buildroot] [PATCH] fbdump: Make fbdump available only to x86/x86_64/arm architectures Markos Chandras
2012-03-14 10:37 ` Thomas Petazzoni
2012-03-14 10:43 ` Markos Chandras
2012-03-14 11:02 ` Thomas Petazzoni
2012-03-14 11:33 ` Markos Chandras
2012-03-14 11:48 ` Markos Chandras
2012-03-14 11:55 ` Thomas Petazzoni
2012-03-14 13:56 ` Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-14 10:40 Markos Chandras
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=4F60A3A8.9000201@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=buildroot@busybox.net \
/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.