Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-embedded
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-embedded@g.o
From: Christopher Friedt <chrisfriedt@...>
Subject: gcc-4.6 / bionic
Date: Tue, 5 Apr 2011 16:15:00 -0400
Has anyone on the list started experimenting with building a bionic
libc cross-toolchain yet with gcc-4.6 [1]?

... seems fairly interesting.

I just finished a small project that put together a fairly minimal
bionic rootfs with nothing but the libc, libstdc++, libm, jamvm,
gnu-classpath, dropbear, & busybox. I was surprised at how well things
actually worked (both arm and x86_64).

Surely there will continue to be some regressions. For example, bionic
traps SIGUSR1 for debugging purposes - so any other binary that uses
that for signalling will need to change it to SIGUSR2. Patching the
build system was fairly straight forward.

I think doing a cross-toolchain with crossdev might even be do-able...
just apply a couple of patches to android's build/ tree, build libc,
libm, libstdc++.

It would be freaking sweet to just be able to 'emerge' libraries for
Android instead of going through the often painful process of
retooling it for Android.mk. It would an accomplishment to bootstrap
gcc, that's for sure.

armv7a-neon-linux-bionic-emerge world

;-)

Cheers,

C

[1] http://www.phoronix.com/scan.php?page=news_item&px=OTI1NQ


Replies:
Re: gcc-4.6 / bionic
-- wireless
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Getting network time early in boot
Next by thread:
Re: gcc-4.6 / bionic
Previous by date:
Re: My Catalyst experience
Next by date:
Re: gcc-4.6 / bionic


Updated Jun 25, 2012

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.