public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Friedt <chrisfriedt@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Cc: Liang Peng <pengliang.sdu@gmail.com>
Subject: [gentoo-embedded] Fwd: JamVM / Bionic
Date: Fri, 8 Jul 2011 07:24:50 -0400	[thread overview]
Message-ID: <CAF4BF-R2MPNdavDTUFZRJyJie5Etskb1821cEfOwZZ-+NLxKUA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin0xLXwVfz8KVoZx3nD2sMezcPL3Q@mail.gmail.com>

Hi again Liang,

Here is a message I sent out with some more information on the jamvm
mailing list.

Incidentally, there is a precompiled toolchain available on the google
code site as well. If you unpack the binaries to
/usr/portage/packages/cross-i686-pc-linux-bionic, and then run emerge
-Kav cross-i686-pc-linux-bionic/{binutils,bionic-kernel-headers,gcc,bionic}
you will have the toolchain installed.

C

---------- Forwarded message ----------
From: Christopher Friedt <chrisfriedt@gmail.com>
Date: Wed, May 18, 2011 at 1:49 PM
Subject: JamVM / Bionic
To: 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



           reply	other threads:[~2011-07-08 12:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BANLkTin0xLXwVfz8KVoZx3nD2sMezcPL3Q@mail.gmail.com>]

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=CAF4BF-R2MPNdavDTUFZRJyJie5Etskb1821cEfOwZZ-+NLxKUA@mail.gmail.com \
    --to=chrisfriedt@gmail.com \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=pengliang.sdu@gmail.com \
    /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