From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: FYI: project using Bionic C library for Gentoo
Date: Thu, 19 May 2011 09:44:07 +0200 [thread overview]
Message-ID: <4DD4CA47.7040100@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 3464 bytes --]
Hi fellow OE people,
this might be of interest for you. Some guy started a project where he
uses Android's bionic C library as the system's libc implementation
(this is at least what it sounds to me).
Since there is an inherent similarity between Gentoo ebuilds and
OpenEmbedded build recipes I thought some people might be interested in
that - of course, for a possible introduction of Bionic into OE. :)
Regards,
Robert
-------- Original-Nachricht --------
Betreff: [Jamvm-general] JamVM / Bionic
Datum: Wed, 18 May 2011 13:49:30 -0400
Von: Christopher Friedt <chrisfriedt@gmail.com>
An: jamvm-general@lists.sourceforge.net
Hi folks,
Sorry if you're receiving this on #gentoo-embedded or another
mailing list as well, but I just wanted to announce a small
project that might be of interest for some people on this list.
I'm introducing Android's Bionic C library into Gentoo's Portage as
new ELIBC and put together a proof of concept overlay that contains
the libc, icu4c, libxml2, libxslt, zlib, gnu-classpath and jamvm
ebuilds.
It's alpha right now, but runs on amd64 / x86 hardware. I haven't
built it yet for arm, but that arch will be my next victim.
If anyone is interested, it would be great if someone could try
building it from scratch and let me know if there are any speed-bumps.
==================================================
I've made tarball snapshots of the portage overlay (i.e. all source),
sysroot, and toolchain available here[1].
A gitorious project has been set up here[2], but I'm not going to
check-in the overlay until a bit more testing is done.
I've also set up a blog to make announcements here[3], and will be
making the first post after checking the overlay into gitorious and
after one or two people can reproduce the build.
Incidentally, if anyone here has an amd64 or x86 arch running Linux
and would like to do take it for a test drive, download the sysroot
from [1], unpack to /usr/i686-pc-linux-bionic and then run the
following:
===================================
#!/bin/sh
for i in proc sys dev tmp; do
mount -o bind /${i} /usr/i686-pc-linux-bionic/${i}
done
chroot /usr/i686-pc-linux-bionic /bin/sh
===================================
Incidentally, if you try to recreate the toolchain, please use the
following:
=====================================================
#!/bin/sh
export PORTDIR_OVERLAY="/usr/local/portage/crossdev-overlay"
export PORTDIR_OVERLAY="${PORTDIR_OVERLAY}
/usr/local/portage/gentoo-bionic-overlay"
emerge =sys-devel/crossdev-20110310 =sys-devel/gnuconfig-20100924
crossdev \
-S \
--g 4.6.0 \
--target i686-pc-linux-bionic
=====================================================
Cheers,
C
[1] http://code.google.com/p/gentoo-bionic
[2] https://gitorious.org/gentoo-bionic
[3] http://gentoo-bionic.blogspot.com
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Jamvm-general mailing list
Jamvm-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jamvm-general
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]
reply other threads:[~2011-05-19 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DD4CA47.7040100@gmx.net \
--to=thebohemian@gmx.net \
--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.