Re: [gentoo-embedded] gcc-4.6 / bionic

There is currently no connection to Linaro. Its just "for fun" and kind of experimental.

I gave a talk on ‎Gentoo Bionic at ELC in February and will be setting up a github repo whenever I have some time for the toolchain, rather than keeping it on Google code.

One thing I've identified is that there are really 2 routes that might be actually independent.

1) using Gentoo Prefix to have a Gentoo install atop of Android. Someone else has already done this recently - saw it on G+)‎. This is really the route for people who would still like to use their Android system but who would also like to emerge packages on top of it in a separate sysroot.

One issue with the toolchain is that definitions in portage itself (/usr/portage/profiles) needs to be modified in order to ‎use bionic instead of glibc, which means that a simple overlay will not work until Gentoo includes those definitions upstream in portage. Bit of a chicken / egg problem.

2) using ‎bionic as the system libc a) with the Android-normal prefix of /system, which is compatible with Android, and b) using the gentoo-normal prefix of /usr which is incompatible with Android. I'm personally aiming for b.

‎In either case, a rather large set of patches need to be maintained just to get things to properly compile against bionic until the bionic headers behave "normally" - e.g. order of includes, conditional defines, conditional includes, include_next, etc. "Proper" (expected) behaviour of libc headers affects virtually everything that uses GNU autotools.

I'll probably maintain a separate github ‎repo for this overlay.

Hope that helps.

C

Sent from my BlackBerry 10 smartphone on the Rogers network.
  Original Message  
From: wireless
Sent: Tuesday, October 22, 2013 9:35 AM
To: chrisfriedt@×××××.com
Subject: Re: [gentoo-embedded] gcc-4.6 / bionic

I know this is old:

On 04/06/11 10:52, Christopher Friedt wrote:
> Also... an important couple of features:
>
> TLS works on certain hardware (e.g. with hardware supported tls, like
> armv7a), but not on all architectures, like in GNU [1], [2]. It's
> probably better to blanket-disable this for now via a portage profile
> variable.
>
> SMP does not currently work OOTB. There are some patches floating
> around[3], with issues that mainly lie outside of bionic, but I the
> 'official' SMP code will be available whenever Honeycomb is
> released[4] ... which is of course whenever Google decides to do
> release Honeycomb.
>
> C
>
> [1] http://gcc.gnu.org/onlinedocs/gcc-3.3.1/gcc/Thread-Local.html#Thread-Local
> [2] http://www.akkadia.org/drepper/tls.pdf
> [3] http://groups.google.com/group/android-platform/browse_thread/thread/de20f1b10703acc2
> [4] http://developer.android.com/sdk/android-3.0-highlights.html#multicore


What the latest with you and BIONIC.....
LINARO connection?


curiously,
James (embedded Gentoo)